Overview
The fastest way to add Latitude to an app is to let your coding agent do it. Latitude publishes a set of Agent Skills that teach an agent (Claude Code, Cursor, Codex, Windsurf, OpenCode, …) how to instrument your code, drive the CLI, and confirm that real traces arrive — following Latitude best practices. There are two entry points, depending on whether you already have a Latitude account.The skills
All skills live in the publiclatitude-dev/skills repo. Most agents can install them with the skills CLI:
| Skill | What it does |
|---|---|
latitude-setup | Zero-account orchestrator: bootstrap → instrument → verify → claim. |
latitude-telemetry | Adds Latitude / OpenTelemetry instrumentation to your app. |
latitude-cli | Installs and drives the latitude CLI. |
latitude-setup builds on the other two, so install all three together for the from-scratch flow.No account yet
If you don’t have a Latitude account, paste this prompt into your coding agent:latitude-setup skill orchestrates the whole zero-account flow:
- Installs the
latitudeCLI and the Latitude skills. - Bootstraps a temporary account — no signup — with an API key and a project.
- Instruments your app (via the
latitude-telemetryskill) against that project. - Runs your real code and inspects the resulting traces, iterating until they look right.
- Cleans up the trace noise and hands you a claim link.
The skill presents a plan and waits for your approval before it edits any code, and it never prints your API key in the chat.
Already have an account
If you’re already signed in, skip the temporary account and point the agent straight at your existing project:LATITUDE_API_KEY and LATITUDE_PROJECT_SLUG when it asks — or connect the MCP server so it can look them up — and it will instrument your app and verify traces the same way.
Once traces are flowing, head to the telemetry guides for provider-specific details, or the CLI and MCP server pages to keep driving Latitude from your terminal or agent.