slaunt
DOCUMENTATION

Troubleshooting

Find the symptom or error text below. The full code list is in Errors.

Connection

SymptomCauseFix
401 invalid_tokenToken missing or expired. Tokens are per client.Claude Code: /mcp → slaunt → Authenticate. Codex: restart to re-login.
400 session header requiredClient isn't keeping Mcp-Session-IdPersist it from the initialize response
404 Unknown MCP sessionSession expired, or reused with another token or clientRe-initialize. If it happens every time, two clients are sharing a session.
Installer: entry already existsA previous Slaunt config is presentRe-run with --overwrite-config

Lifecycle and hooks

SymptomCauseFix
run_begin is invalid while thread state is RUNNINGA run is already active, usually started by a hookWith hooks, don't call run_begin from the model. Otherwise run_end first.
thread_begin is invalid while thread state is RUNNINGRotating threads mid-runrun_end, then thread_begin with new_thread: true
run_step is invalid while thread state is IDLENo active runrun_begin first
Tool calls denied: runtime_stoppedAgent was stopped in Quaero or KillBarIntended. A new prompt starts a fresh run.
Tool calls denied: run_not_activeThe UserPromptSubmit hook didn't start a runRestart the client so hooks and MCP come up together
Codex chats merge or split oddlyHook and tool calls don't share threadIdSee Codex thread routing

Tools and quotas

SymptomCauseFix
A documented tool isn't listedIt's conditionalCheck the conditions
Provider tools missingGateway discovery failed or nothing connectedRead _meta["ai.slaunt/gateway-discovery"] in tools/list
Agent quota has been hitConcurrent agent limitEnd idle sessions in Quaero or upgrade
... quota has been hit for the ... planMonthly quota usedWait for the reset (1st, UTC) or upgrade
Context summary cut off20-word limitShorten it

Still stuck? Contact support with the time, client and exact error text.