openlit CLI ingests events from each vendor’s hook system, normalizes them onto OpenTelemetry’s gen_ai.* and OpenLIT’s coding_agent.* semantic conventions, and ships them to your existing OpenLIT collector. The Agents page’s Coding Agents tab detects them automatically - no controller, no SDK, no code change in your repos.
You only need an OpenLIT instance and the
openlit CLI on each developer’s machine. The CLI talks only to your OpenLIT endpoint. There is no managed cloud for coding-agent telemetry.What you get
Setup & Configure
Install the CLI, wire Claude Code, Cursor, or Codex, and stop tracking when you need to
Analytics
The seeded dashboard - sessions, cost, acceptance, top tools and repos, session outcomes
Sessions
Every coding session, with a full conversational drill-in per session
Users
Per-developer rollups of activity, cost, and code impact
Privacy & Governance
Content capture modes, redaction tiers, and attribution safeguards
Troubleshooting
Diagnose a missing row, silent hooks, or a stale database config
Prerequisites
- A running OpenLIT instance - see Installation if you don’t have one.
- An OpenLIT API key (Settings → API Keys).
- The OTLP endpoint of your OpenLIT collector (defaults to
http://localhost:4318for local installs).

