slaunt
DOCUMENTATION

Claude Code

Use the installer. It adds the server and the hooks, and the hooks are what make Claude Code show up reliably in Quaero and actually stop when stopped:

npx slaunt install --client claude

Manual setup gets you the tools but no hooks, so the model has to call thread_begin/run_begin/run_end itself (install agent instructions so it does):

claude mcp add --transport http slaunt https://central-mcp-ccr-production.up.railway.app/mcp

Then run /mcp, pick slaunt, and choose Authenticate.

What the hooks do

HookEffect
UserPromptSubmitBinds the thread if needed, starts a run, captures the prompt
PreToolUseCalls tool_authorize; a deny blocks the tool call
PostToolUse, SubagentStart, SubagentStopReport activity, capture tool I/O
StopCaptures the final message and ends the run
SessionStart (clear, compact)Re-binds after /clear or compaction

Claude Code fires the first SessionStart before MCP servers connect, which is why UserPromptSubmit handles initial binding.

Because the hook owns the run, a model-issued run_begin while it's RUNNING fails with -32602. Agent instructions written for hook-less clients can trigger this; it's harmless but noisy.

tool_authorize decisions

The PreToolUse guard is how stops take effect mid-turn. If a tool call is unexpectedly blocked, the reason tells you why:

ReasonDecisionMeaning
runtime_authorizedallowRun is active and in scope
runtime_stoppeddenyStopped from Quaero or KillBar. The next prompt starts a fresh run.
run_not_activedenyNo run is RUNNING, usually because UserPromptSubmit failed. Restart Claude Code.
stale_turndenyHook belongs to an earlier turn
scope_mismatchdenyHook session doesn't match the authenticated connection
invalid_metadatadenyHook payload is missing fields