Status & troubleshooting

Check the gateway

Status: web app Monitor → Gateway card (shows “Active: ”, Inbound / Outbound running / not running), and /agent status in chat.

Control: Start, Restart, Stop, Switch… on that card.

Failure reason: View log on that card.

Common issues

Symptom	Cause
/<agent> reports Unknown command	Commands are registered when the gateway boots; a new agent needs a reload. Use /ask <agent>.
The agent is alive but doesn’t reply	listening=false: the agent hasn’t started receiving messages on the bus, or the directory isn’t trusted.
Webhook always returns 401	Clock skew over 300 s, or the body is signed wrong.
Discord bot connects then stops	SERVER MEMBERS or MESSAGE CONTENT intent is off — enable both in the Developer Portal → Bot, then Monitor → Gateway → Restart.
Slack doesn’t see commands	The bot hasn’t been /invited into the channel, or you used / instead of !.