Claude Code chats: tool calls made inside Claude Code subagents leave cards that end as "(stopped)"
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 83/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start in src/main/agent/claude_code.ts, especially the user event handling at lines 361–367 and the shown tracking around lines 515–519. Follow how subagent tool_result blocks reach finishTool, then reproduce with a result carrying a parent_tool_use_id. Done means successful subagent tool calls finish their cards as successful, including in Auto mode.
Written by the indexing model from the issue text.
Description
Found in the Oct 11 audit (at c5f5641).
Where: src/main/agent/claude_code.ts:361-367 (only tool_results with parent_tool_use_id === null call finishTool); :515-519 (canUseTool → showTool creates a card for any tool-use id); :542-553 (close()).
Cause: canUseTool is also called for calls inside Claude Code's Agent/Task subagents and creates a card under that id. The tool_result arrives with parent_tool_use_id set and is ignored.
Reproduction (confirmed with a fake query): approve sub-bash, yield its successful result under parent_tool_use_id: 'agent1', then a success result. The final card is { status: 'error', summary: '… (stopped)' }.
Impact: a successful command looks failed; in Auto mode such cards stay "running" until the turn ends.
Fix: in the 'user' case, also call finishTool for tool_result blocks whose id is in this.shown, whatever the parent.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 2
- Avg merge
- 5h 28m
- Merged PRs (30d)
- 24
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PierrunoYT/patch
-
bug priority: medium severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PierrunoYT/patch#285 ·
Maintainers usually reply within 1 day
-
priority: medium security severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
PierrunoYT/patch#283 ·
Maintainers usually reply within 1 day
-
enhancement priority: medium security severity: medium
Difficulty 5/5 Over a week Newbie friendliness 35/100
PierrunoYT/patch#294 ·
Maintainers usually reply within 1 day
-
priority: low security severity: low
Difficulty 4/5 1-2 days Newbie friendliness 38/100
PierrunoYT/patch#293 ·
Maintainers usually reply within 1 day
-
priority: low security severity: low
Difficulty 3/5 1-2 days Newbie friendliness 67/100
PierrunoYT/patch#292 ·
Maintainers usually reply within 1 day
All issues in PierrunoYT/patch
Similar issues
-
submodule-pointer-regression
Difficulty 1/5 Under an hour Newbie friendliness 72/100
smith-horn/skillsmith#3061 ·
Maintainers usually reply within 1 day
-
area: ops type: test
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
accensa/x402-facilitator-stellar#559 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cosimochellini/one-piece-zero-spoiler#551 ·
Maintainers usually reply within 1 day
-
getWatched() omits __proto__ directories when cwd is setPossibly taken @maxazure claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
-
area:web enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day