claude-code - 💡(How to fix) Fix [Bug] Ultrareview quota consumed on server-side rate limit failures [1 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/user.local/share/claude/versions/2.1.119 (expected in multi-process scenarios)\n at mH6 (/$bunfs/root/src/entrypoints/cli.js:2736:2177)\n at E$8 (/$bunfs/root/src/entrypoints/cli.js:2736:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-24T02:29:38.890Z"},{"error":"Error: 429 {"type":"error","error":{"type":"rate_limit_error","message":"Rate limited"},"request_id":"req_011CaMrXhuGYn5wrv9E18yHh"}\n at generate (/$bunfs/root/src/entrypoints/cli.js:11:55343)\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:4943)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-24T03:04:32.233Z"}]

TL;DR

The issue can be mitigated by ensuring that failed executions due to server errors do not count against the user's quota, and the quota should be restored for the wasted attempts.

Guidance

• Investigate the rate limiting mechanism to understand why it's triggering on repeated runs of /ultrareview for the same PR, despite no review output being generated.
• Verify that the quota deduction logic is correctly handling cases where the execution fails due to server-side errors, such as rate limiting.
• Consider implementing a retry mechanism with exponential backoff for /ultrareview runs that fail due to rate limiting to prevent immediate subsequent failures.
• Review the error handling in the cli.js file, specifically around lines 2736 and 11, to ensure that errors are properly propagated and handled.

Example

No code snippet is provided as the issue does not clearly imply a specific code change.

Notes

The provided error messages suggest a server-side issue with rate limiting, but the exact cause and solution may require further investigation into the server-side logic and configuration.

Recommendation

Apply a workaround by modifying the quota deduction logic to exclude failed executions due to server errors, and restore the wasted attempts for the affected user, as this directly addresses the reported issue and prevents similar problems in the future.