Docs: clarify Auto-Approve Max Requests 'Unlimited' #498
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Review complete. 1 doc-consistency nit flagged.
Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues. |
![roomote[bot]](https://avatars.githubusercontent.com/in/1546624?s=60&v=4){kind=small}
|
|
||
| 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`. |
There was a problem hiding this comment.
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.
|
Closing this PR to redo the Auto-Approve docs update using the new docs-maintainer workflow (topic scan + evidence-based edits). |
Dry-run verification against Roo-Code found that the Max Requests field treats an empty value as Unlimited and serializes it as null when saving settings.\n\nThis updates the docs to reflect the real behavior so users understand how 'Unlimited' works in both UI and settings JSON.
Important
Clarifies 'Max Requests' setting behavior in documentation, indicating blank means 'Unlimited' and is stored as
null.rate-limits-costs.md.nullin JSON.This description was created by
for dd75d5d. You can customize this summary. It will automatically update as commits are pushed.