feat(rate-limit): better feedback in chat

[elianiva]

Related GitHub Issue

Closes: #7922

Roo Code Task Context (Optional)

Description

This PR adds a more user friendly UI to display error caused by rate limit.

Test Procedure

Added a test file along with manual instructions.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Screen.Recording.2025-10-04.at.15.49.48.mov

Documentation Updates

Additional Notes

Get in Touch

@elianiva

---

Important

Enhances chat UI with a user-friendly rate limit error display, including countdown and retry logic, and updates localization files for multiple languages.

• Behavior:
  • Adds user-friendly UI for rate limit errors in chat with countdown and retry mechanism.
  • Implements RateLimitRetryRow component in ChatRow.tsx to display retry status.
  • Updates Task.ts to handle rate limit retries with countdown and retry logic.
• Localization:
  • Adds translations for rate limit retry messages in multiple language files including chat.json for id, it, ja, ko, nl, pl, pt-BR, ru, tr, vi, zh-CN, and zh-TW.
• Testing:
  • Adds RateLimitRetryRow.spec.tsx for testing the new UI component.

^{This description was created by for 03909fc. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

I found some issues that need attention in this PR.

[roomote]

I found some issues that need attention in this PR.

[roomote]

[P2] Mark rate-limit status updates as non-interactive

api_req_retry_delayed is a UI-only status row and shouldn't mutate lastMessageTs. Currently sendRateLimitUpdate calls say() without isNonInteractive, which updates lastMessageTs for new messages in say(). This can interfere with Task.ask's blocking/waiting logic if a status update races with an ask.

Setting isNonInteractive true keeps the message ordering/UI unchanged while avoiding unintended ask lifecycle interactions.

Suggested change

	await this.say("api_req_retry_delayed", undefined, undefined, isPartial, undefined, undefined, {
	await this.say("api_req_retry_delayed", undefined, undefined, isPartial, undefined, undefined, {
	isNonInteractive: true,
	metadata: { rateLimitRetry: payload },
	})

[roomote]

Rooviewer   See task on Roo Cloud

Reviewed PR #8503. Most issues have been resolved. One minor translation inconsistency remains.

• Add isNonInteractive: true to both sendRateLimitUpdate functions in Task.ts (lines 2681 and 3089) to prevent rate limit status updates from interfering with Task.ask's blocking logic
• Indonesian seconds abbreviation consistency - use "dtk" instead of "d" in rateLimitRetry translations (see comment #2403909654)

Previous reviews

• 7b46d60: Review #1
• 0b42d73: Review #2

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[mrubens]

I think @daniel-lxs is working on another version of this - my main feedback was that the rate limit message is separate from the error retry, which I think this is.

[daniel-lxs]

I committed my changes to the wrong branch, woops

[daniel-lxs]

Thank you @elianiva for your contribution! This PR has been superseded by #9088 which incorporates the same functionality with a slightly different approach to the UI. We appreciate your excellent work on improving the retry/rate-limit user experience!