| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
The following comment was made by an LLM, it may be inaccurate: I found some potentially related PRs: Related PRs:
Why they're related: These PRs all deal with error handling and propagation from sub-agents/subagents to parent tasks/sessions. PR #18444 specifically focuses on surfacing terminal provider/API errors from SessionPrompt.prompt() up the chain, which overlaps conceptually with these other error propagation fixes. PR #18389 in particular seems very recent and might warrant checking for overlap. |
Sorry, something went wrong.
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
Sorry, something went wrong.
|
Any update on this? |
Sorry, something went wrong.
|
Rebased on upstream/dev (HEAD: ffa2bff). CI re-running. |
Sorry, something went wrong.
|
Automated PR Cleanup Thank you for contributing to opencode. Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions. This PR was closed because it matched the following cleanup criteria:
PRs created within the last month are not affected by this cleanup. If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate. Thanks again for taking the time to contribute. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Issue for this PR
Closes #17583
Type of change
What does this PR do?
This ensures sub-agent provider failures are visible in the parent task flow. The task tool previously returned normally even when the sub-agent ended with an assistant API error, which made the parent flow appear successful with no clear failure signal.
Now the task tool surfaces non-abort sub-agent assistant errors as tool failures (Sub-agent failed: ...). This makes rate-limit/provider failures visible in the primary flow instead of being silently swallowed.
How did you verify your code works?
Screenshots / recordings
Not a UI layout change. TUI behavior change validated by test coverage.
Checklist
Related: #5204