Problem
Subagent (Task/Agent tool) conversations get written to disk as separate JSONL files — <claude-projects-dir>/<session-id>/subagents/agent-<agentId>.jsonl (with a .meta.json sidecar), tagged isSidechain:true — but none of AgenC's transcript tooling surfaces them:
agenc mission print / agenc session print only read the parent session's own JSONL file. Verified directly: on a mission that had spawned 2 subagents, agenc mission print --format=jsonl produced 1137 isSidechain:false lines and 0 isSidechain:true lines — the subagent content simply isn't in the stream this command reads.agenc session ls --mission <id> lists only the 1 parent session; the subagent files on disk for that mission don't show up as separate listable sessions.agenc mission search doesn't index subagent-only content either. Confirmed with a discriminating test: searched for a string that exists only inside a subagent's transcript (a distinctive Bash command description) — the search returned "No results," while a positive-control search for parent-thread content returned hits fine.
So today the only way to read what a subagent actually did is to manually locate and cat/rg the raw JSONL file by hand — there's no CLI-supported way to list, print, or search subagent transcripts.
Proposed solution
agenc session ls (or a new command, e.g. agenc session subagents <session-id>) lists the subagent sessions spawned by a parent session, with their agentId/short-id.agenc session print / agenc mission print gain a way to target a specific subagent transcript — e.g. agenc session print <session-id> --agent <agentId>, or accepting the subagent's own short ID directly the way parent sessions already work.agenc mission search optionally includes subagent content in its index (or, short of that, the docs/help text note explicitly that subagent transcripts are out of scope, since the current behavior is easy to mistake for "nothing happened" rather than "not indexed").
Filed via Adjutant
Problem
Subagent (Task/Agent tool) conversations get written to disk as separate JSONL files —
<claude-projects-dir>/<session-id>/subagents/agent-<agentId>.jsonl(with a.meta.jsonsidecar), taggedisSidechain:true— but none of AgenC's transcript tooling surfaces them:agenc mission print/agenc session printonly read the parent session's own JSONL file. Verified directly: on a mission that had spawned 2 subagents,agenc mission print --format=jsonlproduced 1137isSidechain:falselines and 0isSidechain:truelines — the subagent content simply isn't in the stream this command reads.agenc session ls --mission <id>lists only the 1 parent session; the subagent files on disk for that mission don't show up as separate listable sessions.agenc mission searchdoesn't index subagent-only content either. Confirmed with a discriminating test: searched for a string that exists only inside a subagent's transcript (a distinctive Bash command description) — the search returned "No results," while a positive-control search for parent-thread content returned hits fine.So today the only way to read what a subagent actually did is to manually locate and
cat/rgthe raw JSONL file by hand — there's no CLI-supported way to list, print, or search subagent transcripts.Proposed solution
agenc session ls(or a new command, e.g.agenc session subagents <session-id>) lists the subagent sessions spawned by a parent session, with their agentId/short-id.agenc session print/agenc mission printgain a way to target a specific subagent transcript — e.g.agenc session print <session-id> --agent <agentId>, or accepting the subagent's own short ID directly the way parent sessions already work.agenc mission searchoptionally includes subagent content in its index (or, short of that, the docs/help text note explicitly that subagent transcripts are out of scope, since the current behavior is easy to mistake for "nothing happened" rather than "not indexed").Filed via Adjutant