agentacct

English · 简体中文

agentacct answers one simple question: what the fuck are my agents actually doing?

See what your coding agents have been working on, across projects and clients: recent activity, tool calls, recorded steps, checks, tokens, and estimated cost. Open a task for its Work Receipt and follow the activity timeline from attempt to result. Built from the local session logs of Claude Code, Codex, Kimi Code, OpenCode, Hermes, and others. No account, no cloud, nothing leaves your computer.

Screenshots show a synthetic demo workspace; your install renders your own local data.

Install

pipx install agentacct
agentacct onboard   # once per machine: finds your agents, sets up a local store, starts the recorder
agentacct tui       # the terminal app

Requires Python >= 3.11 on macOS or Linux; Windows is supported only via WSL. For a native window with no Python, download the signed, notarized macOS app from the latest release (macOS 14+).

Either way, open a new agent session afterwards: hooks and MCP servers bind at session start.

The per-agent setup, a --scope project install, and the uv/venv alternatives are in INSTALL.md.

Follow what happened

Sessions opens with the most recently active tasks. Search by task or project, or choose another sort when you need it. Each receipt brings together the participating sessions, recorded outcome, estimated cost, claims, and check results; its activity timeline comes first, with steps and full check details one click away.

An agent's own "done" is Reported. A Verified result needs current passing checks after the last recorded change. Claims and checks stay separate, and a failed attempt stays visible in the history alongside later results. A recorded failure is useful context, not automatically a request for you to intervene.

A day's work, across every agent you run

Point a work group at a project folder to see which agents worked there and what they did most recently. Open the group for session details and a shared timeline. Each session keeps its own evidence; group totals are sums of the participating sessions, with partial coverage and overlap labeled.

Start with recent activity

The Dashboard shows the latest recorded work across your projects, with its client, activity time, outcome, evidence, and cost. Historical failed checks and blockers remain available in Recorded issues. They do not decide the default order or become a list of things you must fix. Right-click a Recorded issues row to copy a brief from recorded facts.

Understand the usage behind the work

Filter by date, agent, model, or provider—independently, so "Codex on Opus, last 7 days" is one selection instead of a page you reset. This range totals the same rows by agent and by model, and selecting a date narrows the client/model breakdown under the date table. The chart remembers your Fresh or All tokens choice, and the tables show fresh, cache, and total tokens side by side with cache reads and writes separated. Hover a Fresh value for input and output counts.