Documentation Index
Fetch the complete documentation index at: https://docs.latitude.so/llms.txt
Use this file to discover all available pages before exploring further.
Claude Code telemetry
Stream Claude Code conversations into Latitude as traces. After setup, Claude Code turns appear in your project’s Traces view with prompts, responses, tool calls, and tool results.Prerequisites
- A Latitude account with a project
- Claude Code installed locally
- Node.js available on your
PATH
This integration works with local Claude Code surfaces that support hooks, including the CLI, desktop app, and IDE extensions. It does not run inside the hosted Claude web app.
Install
- In Latitude, copy your project slug from the project sidebar.
- Create or copy an API key from Settings → API Keys.
- Run the installer:
Restart and verify
Fully quit and relaunch Claude Code, then run any prompt. Open your Latitude project and go to Traces. The new trace should appear within a few seconds.Disable or uninstall
To pause telemetry temporarily:Manual configuration
If you manage Claude Code settings yourself, add the telemetry command to~/.claude/settings.json:
Captured data and privacy
Treat this as full-fidelity telemetry. Latitude receives the content needed to reconstruct Claude Code turns, including prompts, responses, tool input/output, and system context when available.- Telemetry runs for each turn until disabled or uninstalled.
- Latitude does not redact secrets from captured content.
- Disable telemetry before working with sensitive material you do not want sent to Latitude.
Troubleshooting
No traces appear. Fully quit and relaunch Claude Code, then run a new prompt. Confirm the API key and project slug are correct. Need more diagnostics. SetLATITUDE_DEBUG=1 before running Claude Code. The telemetry command prints diagnostic output when uploads fail.
Wrong project receives traces. Re-run the installer with the correct project slug, or uninstall and install again.