Code Lexica logo

Getting started with Track

Install the CLI, run cdlx init, and watch the team dashboard fill in.

4 min read

Track goes from zero to a live team dashboard in about 5 minutes. You install one CLI, sign in, and pick what to track. No API keys, no proxy, and nothing changes in anyone's workflow.

Install and initialize

Two commands in a terminal:

  • brew install codelexica/tap/cdlx
  • cdlx init — signs you in and lets you pick the repos or directories to track

Which tools are covered

Track ingests Claude Code, Codex, and Cursor end to end today. Want another tool? Email support@codelexica.com; coverage is prioritized by request.

Watch the dashboard fill in

Live sessions show up within a few minutes, and your usage history backfills in the background with a progress indicator on the dashboard. True Cost, what the same usage would cost at full API rates, appears alongside it, broken down by member, model, repository, and tool.

Run cdlx doctor any time to confirm everything is wired up: it checks your login, watched directories, and sidecar in one pass.

Bring in the team

Admins can invite teammates by email from the Members section of Organization Settings, or turn on domain auto-join under Allowed Email Domains so anyone signing in with a company email is added automatically. Each developer runs the same two commands once.

For the full team walkthrough, including the Optimize trial, follow the onboarding guide.

What leaves each machine

Usage metadata only: token counts, model identifiers, tool-call names and result status, session timings, and repository fingerprints. Prompt text, tool arguments, and file contents are never stored; the tracking schema structurally can't carry them.

Still stuck?

If this article didn't answer your question, email us. A real person on our team will get back to you.

Email support