Skip to main content

​
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 public latitude-dev/skills repo. Most agents can install them with the skills CLI:
latitude-setup builds on latitude-cli and latitude-telemetry and ends by building a first Artifact from its own template. latitude-artifacts is for the reports you ask for after that, so the command above installs all four.

​
No account yet

If you don’t have a Latitude account, paste this prompt into your coding agent:
The latitude-setup skill orchestrates the whole zero-account flow:
  1. Installs the latitude CLI and the Latitude skills.
  2. Bootstraps a temporary account — no signup — with an API key and a project.
  3. Instruments your app (via the latitude-telemetry skill) against that project.
  4. Runs your real code and inspects the resulting traces, iterating until they look right.
  5. Cleans up the trace noise and hands you a claim link.
  6. Builds your first Artifact, an HTML page showing what the telemetry captured from the verified session, with a button to claim the workspace, and hands it back with the claim link.
Open the claim link in your browser to take ownership of the temporary account and keep it. Unclaimed temporary accounts expire automatically.
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:
Give the agent your 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, the CLI and MCP server pages to keep driving Latitude from your terminal or agent, or Artifacts to turn that data into reports and dashboards without opening the web app.