Error messages from model provider during a subagent don't make way to primary agent #5204

Activity

1. bcardarella

   added

   bugSomething isn't workingSomething isn't working

   on Dec 7, 2025
2. github-actions commented on Dec 7, 2025

   

   github-actionsBot

   on Dec 7, 2025 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • No errors when usage limit is reached (Claude Pro) #777: No errors when usage limit is reached (Claude Pro) - similar issue where usage/rate limit errors don't show proper feedback
   • TUI should show when it is retrying #4089: TUI should show when it is retrying - related issue about displaying inference engine errors in the TUI
   • Opencode stuck in "generating" #2512: Opencode stuck in "generating" - related issue where the app appears frozen without error feedback

   Feel free to ignore if none of these address your specific case.
3. fghpdf

   added a commit that references this issue on Jan 23, 2026

   fix: propagate subagent retry status to primary agent (anomalyco#5204)

   ...

   6404eeb
4. jettptacek

   marked [FEATURE]: Subagent rate limit hit should surface message like main agent #10724 as a duplicate of this issue on Jan 26, 2026
5. Haohao-end commented on Mar 21, 2026

   

   Haohao-end

   on Mar 21, 2026

   More actions

   I’ve opened a fix for this.

   Summary:

   • TaskTool.execute() was treating a failed child assistant as a successful task result
   • child info.error was ignored, so provider failures could be downgraded into an empty <task_result>
   • the fix now throws on child info.error, which lets the existing parent/orchestrator error path surface the real provider message

   Validation:

   • added a success-path regression test
   • added a provider-error propagation regression test
   • verified with bun test test/tool/task.test.ts
6. thdxr

   assigned

   kitlangton

   on May 3, 2026
7. thdxr

   removed

   bugSomething isn't workingSomething isn't working

   on May 3, 2026
8. github-actions commented on Jul 3, 2026

   

   github-actionsBot

   on Jul 3, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
9. github-actions

   closed this as not plannedon Jul 3, 2026