Show headerless Fable probe quota exhaustion

[lawrencecchen]

Summary

• treats a headerless 429 from the dedicated claude-fable-5 probe as a Fable-only exhausted window
• preserves stale/error behavior for the normal Claude usage endpoint, so transient usage fetch 429s still fall back to last-good data
• marks request-time Claude exhaustion as the Fable feature bucket in /usage-status

Tests

• go test ./...

Live finding

The deployed minimal and fuller Fable probes returned HTTP 429 with no anthropic-ratelimit-* headers, while the ordinary Claude usage endpoint still reported weekly quota. Without this fallback, sr showed the new Fable wk column but left it blank.

---

^{Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.}

---

Summary by cubic

Treat headerless 429s from the dedicated claude-fable-5 probe as Fable-only quota exhaustion so sr shows the Fable week bucket and other Claude models keep their headroom. Also tag request-time exhaustion as the Fable bucket in /usage-status.

• Bug Fixes
  • On headerless 429 from the Fable probe, synthesize a saturated Fable window and set the Feature to the Fable model.
  • Preserve fallback to last-good data for the normal Claude usage API; merge Fable probe windows only when base usage succeeded or when the probe includes primary windows (5h/7d).
  • Add tests for headerless Fable 429 handling and for /usage-status including the Fable window.

^{Written for commit 439cb2b. Summary will update on new commits.}

[coderabbitai]

Warning

Review limit reached

@lawrencecchen, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 5 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 151476af-5dbf-4450-9783-86407c942779

📥 Commits

Reviewing files that changed from the base of the PR and between 523959d and 439cb2b.

📒 Files selected for processing (5)

• cmd/subrouter/sr.go
• internal/agents/claude/store.go
• internal/proxy/claude_ratelimit_routing_test.go
• internal/proxy/proxy.go
• internal/proxy/proxy_websocket_test.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/fable-headerless-probe

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}