Quickstart
The slaunt installer does three things per client: adds the MCP server, runs the OAuth login, and installs hooks that report threads and runs to Quaero and block tool calls once an agent is stopped. Requires Node.js 20+.
macOS / Linux
npx slaunt installWindows (PowerShell)
npx.cmd slaunt@latest installSign in when the browser opens. You may get one login per client, plus one for KillBar; they use separate credentials. Restart the client afterwards, because hooks and MCP servers only load at startup.
To check it worked, start a new chat and ask "What were we working on?" The answer should come from your workspace, and the session should appear in Quaero.
Flags
| Flag | Use when |
|---|---|
--client codex|claude|both | Skipping the interactive prompt, e.g. in scripts |
--overwrite-config | The installer refuses because a Slaunt entry already exists. A backup is written next to each changed file. |
--no-telemetry | Disabling installer analytics (also SLAUNT_TELEMETRY=0 or DO_NOT_TRACK=1) |
Files changed
| File | Change |
|---|---|
~/.claude.json | Adds the slaunt MCP server |
~/.claude/settings.json | Adds Slaunt hooks; your other hooks are kept |
~/.codex/config.toml | Adds [mcp_servers.slaunt]; may be reformatted (comments kept in the backup) |
~/.codex/hooks.json | Adds Slaunt hooks; your other hooks are kept |
Update with npx slaunt@latest update, then restart the client.
Hooks handle the lifecycle, but they don't tell the model when to search or write Slaunt Context. For that, add agent instructions.