Leet Agent Tracker

A local-first dashboard and warehouse for your Claude Code and Codex agent usage. It reads the session logs those tools already write to your machine, imports them into a local DuckDB warehouse, and serves a web UI with cost, token, and activity analytics.

Everything runs on your machine and binds to 127.0.0.1 by default — your usage data never leaves your computer.

Quick start

npx @leettools/leet-agent-tracker serve

That starts the web UI and API server, reports each startup phase, asks whether to open http://localhost:8081, and imports your Claude Code and Codex logs in the background. The dashboard fills in as the import runs. No setup, no account. It keeps importing new sessions while it's running, and you can keep browsing the already-imported data the whole time.

To run a manual import yourself (or if you started with --no-import):

npx @leettools/leet-agent-tracker warehouse ingest

Or install it once and run it like a normal command:

npm install -g @leettools/leet-agent-tracker
leet-agent-tracker serve      # start the web UI
leet-agent-tracker            # show help

Where it looks for logs

By default it scans the standard harness locations, no setup required:

• ~/.codex/sessions
• ~/.codex/archived_sessions
• ~/.claude/projects

Useful options

leet-agent-tracker serve --port 9000          # listen on a different port
leet-agent-tracker serve -y                   # open without asking
leet-agent-tracker serve --no-open            # don't ask or open
leet-agent-tracker serve --no-import          # don't auto-import logs on start
leet-agent-tracker serve --data-root <path>   # strongest data-root override
leet-agent-tracker serve --log-level debug    # show detailed startup phases

The service and CLI default to ~/.leet/agent-tracker. Export AGENT_TRACKER_DATA_ROOT to change that shared default; --data-root overrides it for a single command.

Costs are estimated from public model pricing; connecting a provider account is optional. The first run downloads a platform-specific DuckDB binary (~100 MB), which is then cached.

Requirements

• Node.js 24 or newer