Kraken Discord Bot Status

The all-in-one node is a black box by design: you queue it and it vanishes, sitting quietly waiting for a !generate in some Discord channel. KrakenDiscordBotStatus is the window into that box.

Drop it beside the main node, run it, and it hands you a plain-text report of the bot's current state - whether it's running, how full the queue is, the rate-limit cooldown, whether a token is set, and how many channels the bot is restricted to. If "is it actually up?" matters to you (or to the friends hammering it), this is the node to keep around.

How it works

It has no inputs. On run, it imports the same in-process bot object and config that the all-in-one node uses and formats a status string. That's the key detail: it reads shared module state inside your running ComfyUI process. There's no API, no separate process, no network involved - it can only report on a bot that started in this ComfyUI session.

So ordering matters. If you run the status node before the all-in-one node has ever started the bot, it honestly reports "Bot is NOT RUNNING" and "Token: NOT SET." Not an error, just the truth.

Output

One output: status (STRING). It's not a display node, so wire it into a Show Text node (or any text display) to actually see it. The string looks something like:

Kraken Discord Bot Status

Bot is RUNNING
  Queue: 2/10
  Rate limit: 30s
  Token: SET
  Allowed channels: ALL

That queue line is the genuinely useful bit - 2/10 means requests are waiting behind the current generation, which is your signal that the bot is healthy and busy rather than wedged.

Installing it

Same pack as the all-in-one node - install once and both nodes appear under Kraken/Discord.

cd ComfyUI/custom_nodes
git clone https://github.com/krakenunbound/kraken-discord-bot.git
cd kraken-discord-bot
pip install -r requirements.txt

Or just search "Kraken Discord Bot" in ComfyUI Manager and hit Install, then restart ComfyUI.

Gotchas

• It reports, it doesn't fix. The status node can't start the bot or reset a stuck queue - its whole job is telling you what state the shared bot is in.
• Stale reads. See "NOT RUNNING"? Re-queue the all-in-one node first, then run status again. A bot that died mid-session, or a ComfyUI restart, clears the singleton.
• Mid-generation it still says RUNNING. The queue count is the real signal; a growing N/max means requests are piling up.

Honestly, for a zero-input utility node that's about the whole story. It's a dashboard you didn't know you needed until a friend says "the bot isn't answering" and you'd rather not go spelunking through the ComfyUI console.