Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/advanced-usage/rate-limits-costs.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,8 @@ For reasoning-capable models (for example, Gemini 3 Pro Preview and other models

To further help manage API costs and prevent unexpected expenses, Roo Code includes a "Max Requests" setting for auto-approved actions. This allows you to define a specific limit on how many consecutive API calls Roo Code can make without requiring your explicit re-approval during a task.

**Unlimited behavior:** In Settings, leaving this field blank means **Unlimited** (no request-count limit). In the underlying settings JSON this is stored as `null`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This note explains that blank means Unlimited, but the later “Configuration” bullet still implies “Unlimited” is a selectable option, which can confuse readers. Consider aligning the wording there to “leave blank for Unlimited” so the UI behavior is described consistently.

Fix it with Roo Code or mention @roomote and request a fix.


* **How it works:** If you set a limit (e.g., 5 requests), Roo Code will perform up to 5 auto-approved API calls. Before making the 6th call, it will pause and prompt you to "Reset and Continue," as shown below.
<img src="/img/v3.18.0/v3.18.0-1.png" alt="Warning message indicating the auto-approved request limit has been reached." width="600" />
*Notification when the auto-approved request limit is met.*
Expand Down