Agent observability

Replay what your agents actually did

Replay of 14 coding-agent runs: tool latency, token spend, policy gates and the approvals that stopped a patch.

Demo · simulated data

14Runs
80%Success rate
$0.72Spend
346.8kTokens
38.4sMean run

Implement database migration to add a new 'status' column to the 'transactions' table

acme/payments-api · agent/implement-database-migration-to-ad

0ms1/17 events · $0.06 · 17.3k tok48.3s
agent
tools
gates
repo
planner · plan
  • 0msPLANPlanned 3 file changes4.1s

migrations/20231014_add_status_to_transactions.sql

+1 −0

+ALTER TABLE transactions ADD COLUMN status VARCHAR(20) DEFAULT 'pending';
ALTER TABLE transactions ADD COLUMN created_at TIMESTAMP;

Tool latency

across all 14 runs

toolcallsp50p95fails
shell.exec241.3s2.9s0
http.fetch19587ms2.8s0
db.query13799ms2.6s0
repo.search20303ms432ms0
fs.write3738ms148ms0
fs.read2626ms42ms0

Daily budget

$0.72 of $5.00 spent across 346.8k tokens. Within budget.

14%

This dashboard replays a generated corpus. The interface, replay engine, percentile and cost maths and the diff renderer are all real and tested; the runs they display are synthetic, not captured from a live agent runtime. The Run and RunEvent shapes map closely onto OpenTelemetry spans, so pointing it at real traces is a data-source change rather than a rewrite.

Build something like this

Want this kind of visibility over your own agents?

The dashboard is a demo, but the work behind it isn't: tracing agent runs, attributing cost, and putting approval gates where they actually matter. If you're building something similar and want a hand, tell me what you're working on.

Goes straight to my inbox.