Entelligence-AI / agentplay

# agentplay
**See what your coding agent actually did. Replay every session as a map and a timeline: what it read, what it edited, what failed, and what it shipped. Local, open source, works across Claude Code, Codex, Cursor, Copilot, OpenCode and Kiro.**
 [code] 
That one command finds the agent sessions already on your machine, builds a redacted replay of each one, and opens a local viewer. No account and no API key are required, and your session data never leaves your machine. The only network call is an optional email signup in the viewer, described under Privacy; set `AGENTPLAY_NO_NETWORK=1` to switch it off.
 Screenshot of the bundled demo session (synthetic data). Dark mode: docs/images/explorer-dark.png. 
---
## Contents
- Why this exists
- Install
- Using the viewer
- Supported agents
- Privacy
- Command reference
- The session map format
- How it works
- Configuration
- Development
- Contributing
- Known limitations
- License and credits
## Why this exists
Your agent's transcripts already record what it did: which files it read before editing, which commands it retried, which MCP servers failed, where the context window filled up, and which subagents came back empty. That data sits in `~/.claude`, `~/.codex`, `~/.cursor` and similar folders, and almost nobody looks at it.
agentplay makes that data readable. Every session becomes a map of everything it touched and a timeline you can play back, so you can answer questions like:
- What did the agent read before it edited this file, and what did it never open?
- Which commands failed, and how many times did it retry the same one?
- Where did the context window fill up, and what did the subagents bring back?
- Which PRs, commits and tickets did the session produce?
## Install
You need Python 3.11 or newer. agentplay has **no runtime dependencies** beyond the standard library.
 [code] 
**Setting up with a coding agent?** Point it at `install.md`: step-by-step instructions written for an agent, covering every option above and how to check the viewer is up.
 From source 
 [code] 
 Windows 
The default session folders (`C:\Users\ \.claude`, `.codex`, and so on) are found automatically; no path configuration is needed.
`make` works under Git Bash or MSYS2 (it uses `python\.venv\Scripts\python.exe` on Windows) and in WSL. Without `make`, run the equivalent steps in PowerShell:
 [code] 
The viewer needs the pnpm version pinned in `viewer/package.json` (10.x). An older pnpm, such as 8, rejects the lockfile. `corepack pnpm ...` (as above) runs the pinned version without changing your global pnpm.
To try the viewer on its own, run `pnpm dev` in `viewer/`; it loads three synthetic demo sessions. You can also drag any `agentplay/v1` file onto the page.
## Using the viewer
 [code] 
 [code] 
 Illustrative counts. Builds are incremental, so later runs only rebuild sessions whose transcript changed. 
In the viewer:
- **The map** is a radial tree of everything the session touched: repos, directories and file