StackMap
Subscribe
Explore / agentacct
mikehasa

agentacct

Local-first work receipts for coding agents: reads the session logs Claude Code, Codex, OpenCode and Hermes already write and reports what each task did, what it cost, and whether a check proved it.

667 75 Python MITupdated today
View on GitHubDispute this mapping →
Curator's take

The only tool in this neighbourhood that refuses to take the agent's word for it. Everything else here counts tokens and dollars; agentacct counts work and evidence, and keeps them on separate axes — an agent saying 'done' files the task under Reported, and only a machine check that postdates the newest recorded work earns Verified. Every figure wears its basis (`≈` for estimated, bare ` only for reported), every field carries provenance (client hook, transcript scan, MCP record), and unconnected verifier sources stay honestly labelled 'not connected' instead of quietly scoring zero. macOS app, `agentacct tui`, and a loopback-only JSON API; no account, no telemetry, never touches your provider key. Use it when you are accountable for agent output. Overkill if you only want to know this month's spend.

Mapped by ShipWithAI editors · links verified
README.md

agentacct

tests PyPI Python License: MIT

See what your coding agents actually did — and whether you can trust it — across Claude Code, Codex, OpenCode, and Hermes, without any of it leaving your machine.

agentacct is local-first Agent Work Intelligence for coding agents. It reads the session logs your agents already write on disk — Claude Code, Codex, OpenCode, and Hermes — joins them with the work each session records as it goes, and turns the result into one honest Work Receipt per task: what it did (the commands it ran, the files it touched, the tools it used), what it cost, and how well that is actually proven. Each receipt reads like an audit record, not a vibe: the decision ("the agent says it's done") and the evidence ("a machine check proves it") are separate axes, and every evidence tier has its own shape — an agent's claim can never dress up as verification. See it in the macOS app, a live terminal dashboard (agentacct tui), or over a local JSON API. No browser tab, no hosted server, no account.

A Work Receipt in the macOS app — a Verified task with its summary strip (actions, estimated cost, elapsed, 4/4 checks passed), the receipt dimensions ledger with per-field provenance chips, the live checks with exit codes, and the evidence-coverage card

Private by design. Everything stays on your machine: state is plain local files, the only listener is a loopback-only local JSON API (127.0.0.1) that onboarding starts and agentacct stop stops, and there is no phone-home telemetry, no account, no cloud sync. agentacct never stores or requests a provider API key.

Screenshots show a synthetic demo workspace; your own dashboard renders your machine's real local data.

What you get

The same Task-primary view of your agents' work in the macOS app, in agentacct tui (a live terminal dashboard), and over a local JSON API — everything at a glance across all four agents, in light and dark, with a menu-bar glance always one click away:

agentacct — the macOS app dashboard: recent work with decision badges and evidence-tier pips, a needs-review card, live active work, per-agent plan meters, and the daily fresh-token history for the whole workspace

  • A receipts workbench. Every task your agents touch becomes a row you can hold them to: lifecycle tabs that never inflate a claim (an agent's "done" files under ReportedVerified is reserved for machine-checked completion), an evidence column whose pip shape carries the tier, a checks column with real pass/fail tallies, and a cost column where every figure wears its basis ( marks an estimate — a bare $ is reserved for reported figures). Sorted latest-first, with an attention-first sort one click away when the one blocked task should outrank nine finished ones.

    The Work receipts table — lifecycle tabs (Attention / Verified / Reported / In progress / Observed / Stopped), evidence-tier pips with checked ratios, per-client chips, a checks-passed rail, estimated costs, and recency

  • One Work Receipt per task — what it did, and whether you can trust it. Open a row and the task reads like an audit record (the screenshot at the top): what it was, who ran it, the actions it took (the commands it ran and the files it touched — read straight from each agent

Continue your stack

What teams reach for next — and why each earns a place beside agentacct. Ranked by curator confidence.