Troubleshooting
The bot is not responding
- Check you are allowed. Your admin needs to add you (your number, username, or ID) to the allowlist, or approve your pairing, before the gateway responds. On a pairing channel you may have received a one-time code - see Pair your first channel.
-
Try
/status. If the bot replies, it is working and the problem is elsewhere (model, allowlist for that command, or the specific channel). If/statusalso does nothing, it is likely connectivity or that you are not yet authorised. -
Ask your admin to check the gateway. If you self-host, you can check it yourself:
The bot does not respond in a group
In a group chat the bot only wakes up when it is mentioned or pinged, or when you reply to one of its messages. It deliberately ignores everything else so it does not spam the group.- Mention it by name or
@handle:@YourBot what's the weather today? - Or reply directly to a message it sent.
The bot is slow to respond
- Tool use takes time. Running code, searching the web, or controlling a browser can take 10-30 seconds.
- Thinking mode is slower by design.
/think highreasons before responding;/think off(or a lower level) usually speeds things up.
The bot seems to have forgotten something
There are two different cases:- Lost track within a conversation - the context window filled up and earlier messages dropped out. Use
/compactto summarise and continue, or/resetto start fresh. - Forgot a fact from days ago - that was never saved to durable memory. Ask the bot to remember it explicitly next time: “Remember that …”. See Memory.
I got an error response
| Message | Likely cause |
|---|---|
| ”No credentials found” | The AI provider key is missing or expired - tell your admin |
| ”Rate limit exceeded” | Too many requests to the AI provider - wait a minute and retry |
| ”Model … is not allowed” | The model you picked is not on the allowed list - run /model to see allowed models |
| ”Tool execution denied” | You do not have permission to run that tool |
| ”Gateway unreachable” | The gateway is down - tell your admin |
Commands are not working
- Commands only work if you are authorised. Ask your admin if
/statusand others have no effect. - Send commands as standalone messages (just
/status). Only the inline shortcuts (/help,/status,/whoami,/commands) work embedded in a longer message; most others do not.
I am not receiving voice messages
Voice (TTS) must be enabled by your admin. If it is available, turn it on:/voice instead.
The agent is doing something unexpected
- Send
/stopto interrupt the current response. - Send
/resetto start a fresh session. - If it took an action you did not want (ran a command, wrote a file), tell your admin - they can review the session transcript.
I want to change the AI model
/model on its own shows a picker of the models you are allowed to use. To switch directly, name one:
anthropic/claude-opus-4-6). /status shows the current model.
Still stuck?
Send/status to your admin so they can see what you see. If you self-host or have access to the control panel, the Logs view shows recent activity.