Your weekly limit is at 75%.
Now you know, wherever you are.
AgentsRoom reads the quota bars each AI coding CLI publishes, Claude Code, Codex, Grok Build and Kimi Code, and sends you a notification when one of them crosses a threshold. On the computer, on your phone, or both.
On by default at 50%, 75% and then 90% of every bar, for every account you are signed in to. Right-click the bell next to any bar to give it thresholds of its own, or to silence it.
Current week (all models) is at 76% (alert set at 75%). Resets Sep 24, 04:00
One bell per quota bar. The notification says which provider, which account, which window, and when it resets.
Every Claude, Codex, Grok and Kimi subscription is metered in windows: a rolling one measured in hours, a longer one measured in days, sometimes one per model or per limit group. The CLI shows you the percentage when you ask for it, and tells you loudly when it is at 100%. Between the two, nothing. You find out you were at 90% of the week on a Tuesday when the agent stops on a Wednesday.
AgentsRoom already lists all those bars in one place, the Usage panel in the footer of the app, for every provider and every account you are signed in to. Usage alerts add the missing piece: a bell next to each bar, and a notification when the bar crosses a threshold you chose.
The defaults are 50%, 75% and then 90%, on from the first launch. Three thresholds so the next one is never a surprise and the last one is a final call, none at 100% because by then the CLI says it itself, and Account auto-switch takes over if you have a second account.
One question per page
Four features share the same quota window. Each one answers a different question, and this page answers the first.
Am I about to run out?
This page. A threshold crossed, a notification sent, before the limit.
I am already blocked, what now?
Account auto-switch. The moment the CLI declares the account out of quota, the same conversation continues on another account.
Account auto-switchHow much did this session, project or agent use?
The token usage meter. Input, output, cache, and which project or agent took which share of the window.
Claude Code token usageDid the agent finish?
Agent notifications. Unread badges, desktop alerts and pushes when an agent ends its turn or needs you.
Agent notificationsHow it works
Four steps, none of which needs you to open the panel.
AgentsRoom already reads the bars
The Usage panel polls what each CLI publishes: session and weekly windows for Claude Code, including one per model; the 5-hour window, the weekly window and each limit group for Codex; the weekly window for Grok Build; the 5-hour, 7-day and monthly windows for Kimi Code. With several subscriptions on the same provider, each account has its own bars.
Every bar starts with the defaults
50%, 75% and then 90%, on for every bar from the first launch. The default list lives in Settings, so you can make it 25, 60, 95 or a single value, and every bar that has no thresholds of its own follows it.
A crossing sends one notification
When a bar crosses a threshold, AgentsRoom shows a card inside the app, sends a desktop notification, a push to your phone, or any mix of the three, depending on the switches in Settings. The title names the provider, and the account as soon as the provider has more than one. The body names the bar, the percentage, the threshold that fired and when the window resets.
Then it stays quiet until the reset
A threshold is announced once per window. The bar is refreshed every few minutes, and 80% at every refresh is one banner, not one every ten minutes, and not one more when the app restarts. When the provider publishes a new reset time, the thresholds are rearmed for the next window.
The bell next to each bar
Three states you can read at a glance, two gestures to change them.
The bar follows the default thresholds from Settings.
The bar has thresholds of its own. They survive a change of the defaults.
The bar is muted, or usage alerts are off globally. Muting is remembered on its own, so a muted bar does not wake up the day the defaults change.
Left-click: mute or unmute
The most frequent thing anyone does with a bell is to silence it, so that is the click. Click again to make the bar follow its thresholds again.
Right-click: pick the thresholds
A menu titled Alert me when this line reaches, with 25, 50, 75, 90 and 100% to tick, plus the values already set. From there you can also go back to the defaults, mute the line, or open the settings. Long press and keyboard work too.
Settings, under Notifications
One block in Settings, called Usage alerts, holds everything that is not per bar.
The master switch. Off, every bell shows as crossed and nothing is sent.
Percentages, comma-separated. What every bar without thresholds of its own follows.
A native banner on macOS, Windows and Linux, in the same place the agent notifications appear.
The same title and body as the desktop banner, delivered to the AgentsRoom mobile app on iOS and Android.
The block counts how many bars have their own thresholds, and one button puts them all back on the defaults.
A rule attached to what the bar is, not to what it says
The label you see on a bar, Current week (all models), is a display string: the app's translation of a structured bucket for Claude, the CLI's own wording for a scraped panel. Either can change on the next CLI release. A rule stored on that label would silently fall back to the defaults the day the CLI renames its bar.
So the thresholds you pick are attached to what the bar is: the provider, the account, the time window and the scope, the model or the limit group. Renaming the label changes nothing. A new model is a new bar, with its own rule, which is what you would want.
On your phone, one tap away from the bars
When Also send it to my phone is on, the alert reaches the AgentsRoom mobile app with the same title and body as the desktop banner. Tap it and the app opens straight on the Usage tab of Activity, which mirrors the same bars as the desktop panel, so you see the whole picture, not only the line that fired.
The bells and the thresholds are set on the desktop. The phone receives and shows; it does not change the rule.
FAQ
Which CLIs and which bars are covered?
Every provider that publishes a quota to the Usage panel of AgentsRoom: Claude Code (current session, current week for all models, current week per model), Codex CLI (5-hour window, weekly window, and each limit group), Grok Build (weekly) and Kimi Code (5 hours, 7 days, monthly). A provider added to the panel later is covered without any change to the alerts, because they read the panel, not each CLI.
Do I have to turn it on?
No. Usage alerts are on from the first launch, at 50%, 75% and 90% of every bar. What you may want to change is the channel: the in-app card, the desktop banner and the phone push are three separate switches in Settings, under Notifications.
Will I get a notification at every refresh once I am past 75%?
No. A threshold is announced once per window. AgentsRoom remembers which thresholds it announced and the reset time of the window when it did. It only speaks again when the provider publishes a new reset time, when the percentage has dropped back under the threshold, or when you removed the threshold and put it back.
What if a bar jumps from 40% to 80% between two refreshes?
You get one notification, for the highest threshold crossed, 75%. Both 50% and 75% are marked as announced, so there is no second banner ten minutes later for the lower one.
Can I use a threshold that is not in the menu?
Yes. The default thresholds are a free text field in Settings: type 60, 85 and every bar that follows the defaults uses them. The right-click menu on a bell then lists those values next to 25, 50, 75, 90 and 100.
Does this switch my account when the limit is reached?
No, and on purpose. An alert is what happens before the limit; switching accounts is what happens at the limit, and that is Account auto-switch, a separate feature with its own page. The two work together: the alert tells you the week is at 75%, the switch keeps the agent working when it reaches 100%.
I have two Claude subscriptions. Which one is the alert about?
The title says so. With one account the title is Claude Code · AgentsRoom; as soon as the provider has more than one signed-in account, the account name is added in brackets. Each account has its own bars, its own bells and its own thresholds.
What happens when the CLI renames a bar?
Nothing. A rule is attached to the provider, the account, the time window and the model or limit group, never to the label. The label can change with any CLI release; the rule follows the bar.
Can I set the thresholds from the phone?
Not yet. The phone receives the alert and opens the Usage tab of Activity when you tap it, which shows the same bars as the desktop. The bells and the thresholds are set on the desktop.
Does the alert work when AgentsRoom is not running?
No. The bars are polled by the desktop app, so it has to be open, in the foreground or in the background. What does not have to be open is the Usage panel itself: that is the point.
Is it an email, a Slack message or a webhook?
No. Two channels: a native desktop notification on macOS, Windows and Linux, and a push to the AgentsRoom mobile app on iOS and Android.
You may also like
Account auto-switch
The wall itself: when an account runs out of quota mid-task, the same conversation carries on with another account you are signed in to.
Claude Code token usage
How much each session used, and which project or agent took which share of the window. The bars the alerts read live in the same panel.
Agent notifications
The same channels for a different event: an agent that finished its turn or is waiting for you.
Multiple Claude accounts
Several subscriptions side by side. Each one gets its own bars, its own bells and its own thresholds.
Message queue
Stack prompts and arm one to fire when the window resets, so the credits you paid for get spent.
Mobile companion
The app that receives the push and shows the same bars on the Usage tab of Activity.
Further reading
How Many Tokens Do I Have Left in Claude? The Two Screens to Check.
Your Claude plan is not denominated in tokens, so no screen shows a token balance. What it actually meters, the two screens that do show it, why it drains while you are not typing, and what the September 2026 weekly-window change does to your week.
Claude Code Keeps One Login at a Time. Here Is How to Run Several.
A field guide to running a work account and a personal account on the same machine: the one environment variable that decides which login is active, why the shell approach breaks once you have more than two terminals, and how to pin an account per project.
How to check Claude Code token usage: 4 ways to see what your agents spend
Four ways to check Claude Code token usage: the /cost command, the session transcripts, the ccusage CLI, and a live per-session meter. See exactly what each agent spends.
Stop finding out at 100%
Download AgentsRoom, sign in to your CLIs, and the bells are already on. The next time a week runs hot, you will hear about it at 75%.
Companion app: monitor your agents on the go
Bring your own: Claude, Codex, Antigravity CLI, or other AI provider.
Push bugs and requests straight to your public backlog.