Checkyouragent

Check Your Agent

*Visit checkyouragent.dev*

Claude Code writes a detailed record of every session to ~/.claude/projects.
Check Your Agent turns that record into estimated API-equivalent cost, observed
activity, and supported findings with evidence receipts. The app runs locally:
no accounts, no telemetry, no external calls, and the raw logs are never
modified. Tools like ccusage tell you *what* you used; Check Your Agent helps
you investigate *why* a session was expensive or unusual.

Quick start

With uv (or pipx) installed:

This serves the app on http://127.0.0.1:8000, opens your browser, and uses
~/.claude/projects as the import root when it exists, otherwise ./Data. No
exports handy? Add --demo to explore a bundled, fully synthetic dataset that
exercises every screen (the Import screen also offers Load demo data when
the cache is empty).

The examples use uvx; replace uvx with pipx run if you prefer pipx. For a
persistent command, run uv tool install checkyouragent (or
pipx install checkyouragent). A persistent install also provides the shorter
cya alias, which behaves identically to checkyouragent.

In the app, open Import and choose Sync new and updated, use
Sessions to find sessions worth a closer look, open one to inspect its
timeline, trace, subagents, and supported findings, then use Cost and
Explore for the aggregate views.

What it does

- Import synchronizes Claude Code project folders from a read-only export
  root into a rebuildable SQLite index. Re-importing a changed project rebuilds
  it from source.
- Sessions is an investigation board: supported findings, observed errors,
  subagent fanout, event volume, duration, and estimated cost, with search,
  filters, and sorting.
- The session workspace shows an event timeline with trace lanes, tool
 …