Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-fable-5· anthropicHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION Deep-research / workflow subagent transcripts aren't discovered…

  1. User

    ISSUE DESCRIPTION

    Deep-research / workflow subagent transcripts aren't discovered (nested under subagents/workflows/)

    What I was doing

    Running Claude Code's /deep-research a 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. DiscoverClaudeSessions looks for subagent transcripts exactly one level down:

    <project>/<session>/subagents/agent-<id>.jsonl
    

    and 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>.jsonl
    

    subagents/ here contains only the workflows/ directory, which the loop skips — so the entire tree underneath is never discovered. Each transcript carries isSidechain: true and an accompanying agent-<id>.meta.json whose agentType is workflow-subagent.

    Concretely, in one session three /deep-research runs produced 312 agent-*.jsonl files under subagents/workflows/, and zero directly under subagents/. 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 into subagents/workflows/<wf_id>/) instead of only reading its top level, and treat agent-*.jsonl found 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 using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to 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-$

  2. Claude Assistant

    Now I'll update the discovery loop to walk subagents/ recursively:

  3. Claude Assistant

    Now add the helper function. First check imports:

  4. Claude Assistant

    Now update FindClaudeSourceFile's subagent lookup to also find nested files:

  5. Claude Assistant

    Now check for other code that assumes the parent dir of a subagent transcript is subagents or derives the parent session from the path:

  6. Claude Assistant

    Build passes. Now create a temporary reproduction script (will be removed before submitting):

  7. Claude Assistant

    The fix works. Let me verify the test fails on the original code (reproduce the bug):

  8. Claude Assistant

    One failure in a Cortex test unrelated to my change. Verify it fails on original code too:

  9. Claude Assistant

    Pre-existing failure (likely because tests run as root, so permission-based read errors don't trigger). Unrelated to my change. Run discovery-related tests explicitly and vet:

  10. Claude Assistant

    Vet is clean. Let me quickly check whether the file watcher recursively watches directories (so nested workflow dirs also get events):

  11. Claude Assistant

    Everything looks good. Run the broader test suite to check for other affected packages:

  12. Claude Assistant

    These failures are environment-related ($HOME not set). Set it and rerun:

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.