Diagnose a Stopped Channel with the MCP

The diagnose_stopped_channel prompt asks a model to find out why a channel stopped or is not processing messages. In Claude Code, with the server added under the name qie, it runs as /qie:diagnose_stopped_channel. Other clients start a prompt in their own way, where they support prompts. Codex does not support prompts, so ask it for the same work in your own words (see Connecting Codex).

Arguments

Argument	Required	Holds
channel	Yes	The channel's name or id.

What the model is asked to do

1. Find the channel, and read its state, queue counts and recent throughput.
2. Read the channel's recent log, and the engine log from around the time it stopped.
3. Read the channel and its recent changes, to see whether a change lines up with when it stopped.
4. Report the most likely cause, the evidence for it, and what it would do about it.

The model does not start, stop or restart the channel until you say so.