ISSUE DESCRIPTION Deep-research / workflow subagent transcripts aren't discovered…
- User
ISSUE DESCRIPTION
Deep-research / workflow subagent transcripts aren't discovered (nested under subagents/workflows/)
What I was doing
Running Claude Code's
/deep-researcha few times, then looking for those sessions in agentsview. Each run fans out into ~100 subagents and leaves a large pile of per-agent transcripts on disk — exactly the kind of session history I'd want to browse and analyze in agentsview after the fact.What happened
None of the deep-research subagent transcripts show up in agentsview. The parent session imports fine; the ~100 subagents per run are invisible.
The cause is a path-depth assumption in discovery.
DiscoverClaudeSessionslooks for subagent transcripts exactly one level down:<project>/<session>/subagents/agent-<id>.jsonland in that loop it skips any directory entry:
// internal/parser/discovery.go ~L359 for _, sub := range subFiles { if sub.IsDir() { continue // ← never descends } name := sub.Name() if !strings.HasPrefix(name, "agent-") || !strings.HasSuffix(name, ".jsonl") { continue } ... }But deep-research (and Workflow-tool runs generally) write their subagent transcripts one level deeper, grouped by workflow id:
<project>/<session>/subagents/workflows/<wf_id>/agent-<id>.jsonlsubagents/here contains only theworkflows/directory, which the loop skips — so the entire tree underneath is never discovered. Each transcript carriesisSidechain: trueand an accompanyingagent-<id>.meta.jsonwhoseagentTypeisworkflow-subagent.Concretely, in one session three
/deep-researchruns produced 312agent-*.jsonlfiles undersubagents/workflows/, and zero directly undersubagents/. All 312 are currently dropped.Why it matters
Deep research is one of the highest-value things to capture: a single invocation can spawn a hundred subagents and burn a lot of tokens, and right now that whole tree is invisible in agentsview — no transcripts, no token/usage attribution, no way to review what the subagents actually did. As more people lean on workflow-style fan-out, this is a growing blind spot.
The fix looks small: walk
subagents/recursively (or specifically also descend intosubagents/workflows/<wf_id>/) instead of only reading its top level, and treatagent-*.jsonlfound anywhere beneath it the same way. The.meta.json(agentType: workflow-subagent) is available alongside each transcript if the workflow grouping is worth surfacing in the UI.Interface
No new interfaces are introduced.
ADDITIONAL ADVICE
Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use
git checkout <file>to restore the file to its original state. You can also reset all changes in the repository usinggit reset --hardcommand. Additionally, you can usegit stashandgit stash popto temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you callsubmit) usinggit statusorgit diffcommands. However you don't need to usegit addorgit commitbefore submitting your changes. In fact,submitonly submits currently unstaged changes because it usesgit diffto get the changes that need to be submitted.CHECKLIST
Before submitting your solution, please go over the following checklist and make sure you've done everything:
- If an error was reported in the issue description, I have successfully reproduced it.
- If an error was reported in the issue description, I have confirmed that my fix resolves the error.
- I have thought about edge cases and made sure my fix handles them as well.
- I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.
Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!
(Current directory: /agentsview, current file: none) bash-$
- Assistant
I'll start by exploring the repository structure and locating the discovery code that skips nested workflow subagent transcripts.
- Assistant
I'll inspect the discovery code around the subagent path-depth check and related tests.
- Assistant
Next I'll read
DiscoverClaudeSessionsand the existing subagent discovery tests. - Assistant
I'll inspect the full Claude discovery helpers and the subagent-related discovery tests next.
- Assistant
I'll search for other path assumptions around
subagentsand review how similar recursive discovery is done elsewhere. - Assistant
The sync engine also hardcodes subagent path depth — I'll inspect that next.
- Assistant
I'll check how Claude subagent parent linkage is derived from the path.
- Assistant
Let me look at how parent session ID is extracted for Claude sessions - likely from file path or JSONL content.
- Assistant
I'll also check the watch path handling and any docs that describe the expected directory layout.
- Assistant
I'll check how SyncAll discovers Claude sessions and whether classification needs the nested workflow layout.
- Assistant
Let me look at FindSourceFile for Claude as well.
- Assistant
I need to see how Claude session IDs and project names are derived from the discovered path.
- Assistant
Checking the Go version and coding style conventions next.
- Assistant
Checking how processClaude uses the Project field from discovery.
- Assistant
Implementing recursive subagent discovery in
discovery.goand nested-path classification in the sync engine. - Assistant
Updating
FindClaudeSourceFileto search nested workflow subagent paths. - Assistant
Let me open that area.
- Assistant
I'll replace the subagent search section to also walk nested directories.
- Assistant
I'll update sync path classification to accept nested workflow subagent paths.
- Assistant
I'll update the Claude subagent classification to accept nested paths as long as parts[2] == "subagents" and the basename is agent-*.jsonl.
- Assistant
I introduced extra closing braces in
engine.go— fixing that now. - Assistant
Writing a quick reproduction script and running the related unit tests.
- Assistant
I'll set the Go module cache and retry.
- Assistant
I'll put a temporary repro under the module tree so it can import
internal/. - Assistant
Discovery works. Next I'll exercise path classification and a full end-to-end sync.
- Assistant
Let me check NewEngine signature and how setupTestEnv creates the engine.
- Assistant
Let me update the sync repro script with correct API, and also check SyncAll signature.
- Assistant
Let me look at dbtest.OpenTestDB
- Assistant
I'll verify path classification works for nested workflows so live file watching picks them up.
- Assistant
Let me write a quick test that uses SyncPaths on a nested path only (without discovery bulk).
- Assistant
Running discovery and related sync tests.
- Assistant
Tests pass. I'll format each package separately and remove the temporary repro helpers.
- Assistant
I'll revert the incidental test-file formatting and inspect
TestSyncPathsClaudeRejectsNested. - Assistant
Confirming the nested rejection test is unrelated; formatting only my intentional code changes.
- Assistant
I'll quickly check whether the file watcher walks nested subagent directories.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.5-35B-A3BCompare side by side →
Qwen/Qwen3.5-35B-A3BCompare side by side →