Who it is forA developer who runs Claude Code with subagents and wants to know which ones returned useful results.
The problemSubagent work is easy to lose in a long session, so it is unclear which subagents contributed and which came back empty.
The outcomeA per-subagent view of the session showing each subagent's work in its own lane and its position in the timeline.
What you need first
- Python 3.11 or newer
- uv, pipx, or pip to run agentplay
- Existing session transcripts from a supported agent such as Claude Code, Codex, or Cursor on the same machine
Steps
- Run
uvx agentplayto build maps and open the viewer. - Open a Claude Code session that used subagents.
- Select a single subagent with the agent lens so the explorer re-scopes to it.
- Play the timeline to see what that subagent read, edited, and produced.
Prompt for your agent
Using the agentplay repo at https://github.com/Entelligence-AI/agentplay, run `uvx agentplay`, open the Claude Code session <session name or id>, and use the agent lens to scope to each subagent. Report which subagents produced edits or outputs and which came back with nothing. Verify by checking each subagent lane against its entries on the timeline.
Caveat. Subagent prompts and descriptions are not recorded, so you can see what each subagent did but not the instructions it was given.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page