Troubleshooting

Used /new and Now Your Bot Won’t Respond?

A fast recovery flow for the common case where your agent goes silent after resetting or starting a new session.

Community reports often sound like this: "I hit /new and now my bot won’t respond in Discord or dashboard." Most of the time, this is recoverable and does not mean your bot is gone.

Key idea: /new resets chat context. It doesn’t delete your bot. Silence after that usually means a session/channel mismatch or a permission/integration edge case.

2-minute recovery checklist

1) Verify you’re testing in the correct place

Test one clean message in the same surface where it previously worked (dashboard chat, Discord DM, or server channel). Don’t switch surfaces while debugging.

2) Send a tiny ping first

Use a minimal prompt such as:

Reply with exactly: OK-ALIVE

If this works, your bot is alive and your previous request was likely too large or context-heavy.

3) Re-check Discord channel restrictions

If DM works but server channel does not, check channel overrides and Integrations restrictions for:

View Channel
Send Messages
Use Application Commands
Thread/forum reply permissions (if applicable)

4) Start a fresh tiny task in a fresh chat

If your prior thread was bloated, start clean and ask for one small action only. Long/bloated chats can make agents appear unresponsive.

Common root causes after /new

Context reset confusion: you expected old context to carry over automatically.
Surface mismatch: dashboard and Discord are separate conversations.
Channel override drift: bot can read but cannot send in one channel.
Thread/forum mismatch: testing in a location with different permissions.
Oversized first request: immediate heavy prompt causes timeout/stall perception.

Don’t do this: paste massive old chat history into a brand-new session to "restore memory." It usually makes performance worse.

Known-good test flow

Open one surface only (e.g., Discord DM).
Send: Reply with OK-ALIVE.
Send: What channel/surface are you replying from?
Send one tiny task (single-step, no tools).
Only then move to bigger requests.

If it still fails everywhere

Escalate with a clean packet so support can reproduce quickly:

Issue: Bot silent after /new Where tested: [dashboard chat | Discord DM | channel name] Exact test prompt: "Reply with OK-ALIVE" Observed result: [no reply / typing then stop / error text] What I already checked: [permissions, integrations, fresh session] Started happening: [time + timezone]

Bottom line: /new doesn’t kill your bot. In most cases, a clean-surface ping + permission check + fresh small task restores normal behavior quickly.