feat(tui): show user-facing status when rate-limited (429) or retrying#2056
feat(tui): show user-facing status when rate-limited (429) or retrying#2056bj456736 wants to merge 1 commit into
Conversation
When a provider returns 429 or any other retryable error, the CLI previously spun silently with no user feedback. This change surfaces a warning status message in the TUI so users know why the system is waiting. - 429: "Rate limited (429), retrying in Xs… (Y/Z)" - Other: "Request failed, retrying in Xs… (Y/Z)" Fixes MoonshotAI#2025
|
commit: |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d367073635
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| case 'turn.step.interrupted': this.handleStepInterrupted(event); break; | ||
| case 'turn.step.completed': this.handleStepCompleted(event); break; | ||
| case 'turn.step.retrying': break; | ||
| case 'turn.step.retrying': this.handleStepRetrying(event); break; |
There was a problem hiding this comment.
In subagent/AgentSwarm flows, handleEvent returns from routeChildAgentEvent(event) before this switch, and that route has no handling for turn.step.retrying, so a child agent that hits a 429 or other retryable provider error is still swallowed silently while the Agent card waits. Please either let retry events fall through or render the same retry status from the subagent route so the new user-facing feedback also covers delegated tasks.
Useful? React with 👍 / 👎.
1 participant
When a provider returns 429 or any other retryable error, the CLI previously spun silently with no user feedback. This change surfaces a warning status message in the TUI so users know why the system is waiting.
Fixes #2025