Missing Rate Limit (429) / Provider Warning UI Feedback for Sub-Agents in TUI

[OyuNet]

Description

When using the TUI, if the model encounters a rate limit or a different kind of error during without sub-agents, the TUI correctly displays a warning notification in the bottom left corner like "You are rate-limited", "Your daily token quota exceeded".

However, if the main agent spawns sub-agents and one of these sub-agents hits a rate limit while running, no warning is propagated to the UI. The main TUI view shows no indication of the limit, and clicking on the specific sub-agent to open its detailed view also shows no rate limit warnings or errors. This leaves the user unaware that the process is hanging or being blocked due to API limits.

Plugins

None

OpenCode version

1.2.26

Steps to reproduce

1. Start OpenCode in TUI mode.
2. Provide a prompt that requires the agent to spawn multiple sub-agents.
3. Artificially trigger a rate limit from the provider (or use a provider/key with very low limits).
4. Observe the main TUI view while the sub-agents are active; no rate limit warning appears.
5. Expand/click on the active sub-agent to view its details; the detailed view also fails to display the rate limit warning.
6. Compare this to running a simple linear prompt where the bottom-left warning successfully appears.

Screenshot and/or share link

No response

Operating System

macOS 26.0.1

Terminal

Warp

[github-actions]

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

• Error messages from model provider during a subagent don't make way to primary agent #5204: Error messages from model provider during a subagent don't make way to primary agent — describes the same problem where rate limit errors in sub-agents are not surfaced in the main TUI view.

[OyuNet]

While this is highly related to #5204, there is a key difference. In #5204, the user was able to see the error by clicking into the sub-agent details. In my case (on v1.2.26), the rate limit warning is completely hidden, even when expanding the specific sub-agent.

Also, I noticed there was a PR merged for #5204 back in January. Since I'm experiencing this on v1.2.26, this might be a regression or a case where certain provider errors aren't being caught by that previous fix. I'd be happy to look into the code and open a PR if pointed in the right direction.