心宝❤全局密钥管理

Every API-node pack has the same hygiene problem: every Banana and ModelScope node in your graph wants a key, and if you paste the key into each one, you're one "share workflow" click away from leaking it. This node is the pack's answer - a single global key store that backfills the key into every node that leaves its key field blank, plus a purge button for when you want to export a workflow without the keys in it.

It's bookkeeping, not generation. No pixels, no API calls; it manages the pack's key state so the rest of the nodes can default to "blank field means use the global key."

The two inputs

• banana_global_api_key - the global key for the Banana/Gemini generation nodes and the multimodal caption node. Fill it in and every 心宝❤Banana-family node whose key field is empty picks it up, instead of you filling each one by hand.
• modelscope_global_api_key - the same, but for the ModelScope family: 心宝❤魔搭文生图 (XinbaoModelScopeImageGenerate) and the ModelScope channel of the caption node.

Leave both blank and nothing happens - it's a fill-in-when-needed node.

The one output

status (STRING) - a report of what the node did: which keys were set, which nodes got backfilled, and (on purge) what got cleaned. Wire it to a text preview to read it; it's informational.

The workflow it enables

The intended pattern is in the tooltips: set the global key here, keep every per-node key field empty, and the pack fills them in at runtime. Then when you want to share or export the workflow, run the purge function (the display name is 全局密钥管理 - global key management; "purge" is the export side) and the keys get wiped from the graph so the shared JSON doesn't carry your credentials.

This matters more than it looks. The KB's external-api-nodes doc is blunt about API-wrapper nodes: they ship a credential and make outbound calls by design, which is exactly the shape of the thing that got weaponized once in this ecosystem. The author's own README repeats the rule - keys live in config.ini or the node field, never in shared workflows. This node is the enforcement mechanism for that rule.

Installing

Ships in comfyui-banana-li-linux:

cd ComfyUI/custom_nodes
git clone https://github.com/98624017/comfyui-banana-li-linux

Restart ComfyUI. No dependencies beyond the pack's base set.

Two gotchas. First, the backfill only reaches nodes that leave their key field genuinely empty - a node with a stale key typed in will use that stale key and silently fail when it expires. Second, purge wipes both global keys and the backfilled values together, so run it as the last step before export, not as part of a normal run - otherwise every generation after it will need keys re-entered. If you keep hitting that, leave the keys in config.ini instead and use this node purely as the global-field convenience.