macOS: Settings cog (appearance + quit) and tab toggle in the top bar#482
Conversation
… bar
- Move the Usage/Live segmented toggle up into the header row, next to the
Codex/Claude provider toggle.
- Add a gear (settings) button on the right of that bar. It toggles a Settings
tab with:
- Appearance — Light / Dark / System (follow system), persisted in the
"appearance" UserDefault and applied to the whole popover (chrome + content)
by AppDelegate via popover.appearance, live as it changes.
- Quit Burn (the global ⌘Q still works too).
- Picking Usage/Live also dismisses Settings.
This re-lands the settings work that never reached main (it was committed to the
live-burn branch after #480 merged).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Review limit reached
More reviews will be available in 36 minutes and 48 seconds. Learn how PR review limits work. To continue reviewing without waiting, enable usage-based billing in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Two causes, both fixed: 1. Stale ledger. `burn summary` is read-only now (#479) and the background `ingest --watch` doesn't keep up (manual ingest pulled in 3290 backlogged turns), so the polled totals didn't move. Replace the watch with a one-shot incremental `burn ingest` at the top of each poll (BurnLedger.ingest()) — a warm sweep is ~1–3s, so the poll cadence is now 2.5s. 2. Negative/clamped rate. The rate was the delta between two trailing-5-min window totals, which dips negative as old turns age out of the window and was clamped to 0 — reading as "no usage". Replace with a moving average: each poll queries the trailing 60s and divides, which is non-negative and robust to the window sliding and to late ingests. The cumulative line is now the integral of that rate (a monotonic session total). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 participant
Summary
appearanceUserDefault and applied to the whole popover (chrome + content) byAppDelegateviapopover.appearance, updating live as you change it.This re-lands the settings work that never reached main — it had been committed to the live-burn branch after #480 was merged.
🤖 Generated with Claude Code