Subagent History
Read what the children Claude Code, Codex, Cursor, Grok and Devin spawned actually did — their conversation, tool calls and results — and reply to one without leaving its log.
Delegation used to be a spinner and a summary. A child agent would spin up, do real work, then disappear — leaving you with whatever the parent chose to tell you about it. When the summary was thin or wrong, there was nothing to check it against.
Subagent history keeps those children readable.
Find the count
When Claude Code, Codex, Cursor, Grok or Devin spawns children, a count appears beside the delegation badge on that terminal. It opens a searchable list of every subagent from that run — the panel is titled Native subagents — Children of this terminal's session.
Finished children stay in the list. A delegation is still readable after its spinner has gone.
Every child is bound to the exact parent that spawned it — never the newest session, never a guess from a shared folder. With four terminals working in the same repo, a delegation cannot be attributed to the wrong one. The names come from the spawn itself: the task title you would recognise, not an id.
Read one
Pick a subagent and you get:
- its conversation
- its tool calls
- its results
What it actually did — not the parent's summary of it.
Follow a running child
| Control | What it does |
|---|---|
| Follow log | Streams a child that is still working |
| Earlier logs | Pages back through a long run |
| Latest | Jumps to the end |
Reply to a child
A composer sits under the log: Ask for an update or suggest a change…. Enter sends, Shift+Enter keeps the newline, and the log follows from the tail so your reply lands where you were already reading.
A native child has no input of its own — the parent CLI owns it. So Send to subagent delivers your message to the parent conversation, addressed to that exact child id with an instruction to resume it rather than spawn a new one. You can watch the hand-off land in the parent's transcript.
If the parent terminal is gone, has moved to another session, or has exited, Send keeps your draft and tells you which of those happened rather than dropping it.
Carry a finding back yourself
- Copy ID — the subagent's identifier, for reference.
- Copy follow-up for parent — the composed hand-off as text, for when you would rather paste it into the parent conversation and see it go.
Why it goes through the parent
1DevTool never writes to a native child directly. Every message is relayed by the parent that owns it.
That is deliberate: a subagent that two things are driving is a subagent whose transcript no longer explains its own behaviour. Routing through the parent keeps one writer on the conversation, so the record you came here to read stays trustworthy.