Retry
npm test, run twice#33 · 2m23s
npm testexit 1#28npm testattempt 2#33
See when your agent repeats a failed command.
agentplay · open source
Turn the agent transcripts already on your machine into interactive maps and timelines. Inspect what happened without digging through logs.
$ uvx agentplayThe map
Explore repositories, commands, MCP tools, models, subagents, and outputs in one interactive map.
Signals
Jump straight to retries, delays, errors, context compactions, model switches, and PRs marked on the replay timeline.
npm test, run twice#33 · 2m23s
npm testexit 1#28npm testattempt 2#33See when your agent repeats a failed command.
Slow tool call#34 · 2m36s
12.8son npm test, #33
Find slow tool calls, model responses, and periods of inactivity.
Compaction#43 · 3m26s
168.4K23.1Ktokens
See when context was compressed, with token counts before and after.
Produced#53 · 4m07s
Jump to where a PR was opened during the session.
Model switch#44 · 3m29s
Switched right after the compaction at #43.
See when your agent switched models during execution.
Errors2 unique
non-zero exit#29Tool calloverloaded#35LLM / API · retriedInspect failures by type, from shell commands to MCP and model errors.
Install
Python 3.11 or newer. No runtime dependencies, no account, no API key. Later runs rebuild only sessions whose transcript changed.
Run itpick one
$ uvx agentplay$ pipx run agentplay$ pip install agentplayCommands
agentplayBuild new or changed sessions, start the local server and open the replay.agentplay buildBuild maps only and print the summary.agentplay listList built sessions, newest first.agentplay exportWrite one session map to .json or .json.gz.agentplay importAdd map files from a teammate or another machine.agentplay agentsShow which supported agents were found.Research · Whitepaper
Turn code review feedback into reusable learnings, connecting what went wrong in one session to what agents do next.
WHITEPAPER // 2026
Self-Improving Coding Agents
Aiswarya Sankar · Entelligence · Sep 30, 2026
3Trace forensics: down to the step and turn
For each comment we compute a causal path, the minimal chain of events leading from what the agent knew to the flagged edit. For the attribution bug the path is four events long. The subagent had the right answer and the main agent never received it. The diff can’t show that. Only the trace can.
Review comment · views.py L140 · PR #4182Attribution contract expects cohort_id, not user_id.
Apache 2.0 licensed, with support for multiple coding agents and no hosted infrastructure required.
No. Maps are built on your machine and served on 127.0.0.1. There is no telemetry, update check or upload, and the replay page loads no remote fonts or scripts.
No. agentplay reads the transcripts your agents already write to disk. It never calls an agent vendor’s API.
Cursor does not write billed usage to disk, and Kiro bills in credits. Every event, file and error from those sessions is still replayed.
From public list prices, with cache reads at 0.1× and cache writes at 1.25× the input rate. Plan, enterprise and batch pricing are not modelled.
agentplay export writes one map to .json or .json.gz and reports which repo names and how many paths it holds. The recipient runs agentplay import or drops the file onto the replay page.
A map stops at its first 20,000 events and is flagged truncated. Transcripts over 512 MB are skipped.
macOS and Linux. Windows is supported by the parsers and less tested. On WSL, point AGENTPLAY_CLAUDE_HOMES at both homes.
Entelligence maintains agentplay under the Apache License 2.0. The hosted team edition is separate; the open-source tool does not depend on it.
Turn transcripts already stored on your machine into interactive replays with uvx agentplay.
$ uvx agentplay