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, GitHub Copilot CLI, Kimi Code, Cursor, Antigravity, OpenCode Go and the Z.AI Coding Plan, 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, Kimi, Cursor, Antigravity, OpenCode Go and Z.AI Coding Plan 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 a quota rule can take over from there if you have a second account.
One question per page
The same quota window raises different questions. Each page answers one, 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?
A quota rule, written in the same Usage panel: when the bar reaches the threshold you set, the running agents move to another account and the same conversation continues. The account auto-switch page describes the handover.
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 much of my week does one session use?
Robin Hood, the session vs weekly limit tracker. It measures on real subscriptions how much of the week one full 5-hour session uses, per provider and plan, and flags the day a provider changes its limits.
Session vs weekly limit trackerHow 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 or monthly window for Grok Build; the billing cycle for Cursor (included usage, plus its Auto and API pools); the 5-hour and weekly windows of each Antigravity model pool (Gemini, then Claude and GPT); the 5-hour, 7-day and monthly windows for Kimi Code; the 5-hour, weekly and monthly windows for OpenCode Go; the 5-hour and weekly windows of the Z.AI Coding Plan. GitHub Copilot CLI exposes the monthly premium allowance of its active CLI account. 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. If that bar had reached 90% or more, the reset itself is announced: you can code again.
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.
Chips to tick: 25, 50, 75, 90 and 100%, at least one stays on. 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.
Quota kick-off: the countdown starts before you do
A 5-hour session or a 7-day limit only starts counting with your first message, and refills a fixed time after it. The Quota kick-off card, in the same Usage panel, sends that one message for you, earlier. Kicked off at 07:00, a session you start at 09:00 refills at 12:00 instead of 14:00.
Filmed in the real app: the Quota kick-off card of the Usage panel, set to At set times on the Claude session, weekdays at 07:00. The timetable shows the kick-off pin and the refill it brings at 12:00 instead of 14:00. Kick off now sends one line to Haiku through your own CLI and answers Kicked off a few seconds later, with no agent and no tab.
Without a kick-off
You sit down at 09:00 and send your first prompt. The 5-hour countdown starts now.
Refills at 14:00
With a kick-off at 07:00
AgentsRoom sends one short message at 07:00. The countdown has been running for two hours when you sit down.
Refills at 12:00 · 2 hours sooner
One setting per quota
Every quota picks Off, or one of two modes. A 5-hour session takes either; a weekly limit takes Back to back, since its next week simply follows the last one.
The quota restarts the moment it refills, with no idle gap. The next week starts as soon as the previous one ends, without waiting for your next message.
Days and times you pick, 07:00 on weekdays for example. A kick-off leaves at each time, unless the quota is already running, in which case nothing is sent. On a session lane you can also click the timetable to drop a kick-off at that hour.
A single short line, sent to the cheapest model that draws from that quota, Haiku for a Claude session, through the account's own CLI, in the background. No agent, no tab, no terminal.
The 5-hour sessions of Claude, Codex and Antigravity, and the weekly limits of Codex and Antigravity, which also start at the first message after the previous week. Claude's weekly limit refills on a fixed date no message can move, so it is not listed; neither are providers whose period is fixed or rolling, where a message would start nothing.
A kick-off fires while AgentsRoom is open. One missed while the computer was asleep leaves when it wakes up, and the wake setting used by scheduled tasks, Wake the machine for scheduled triggers, also wakes the machine to hold the exact time.
Each account's quotas have their own setting, and the message goes through that account's own CLI, so a kick-off never debits the wrong subscription.
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 or monthly), GitHub Copilot CLI (monthly premium allowance of the active CLI account), Kimi Code (5 hours, 7 days, monthly), Cursor (billing cycle: included usage, Auto and API pools), Antigravity (5 hours and weekly, per model pool: Gemini, then Claude and GPT), OpenCode Go (5 hours, weekly, monthly) and the Z.AI Coding Plan (5 hours, weekly). A provider added to the panel later is covered without any change to the alerts, because they read the panel, not each CLI. Copilot needs a CLI version exposing account quotas through its SDK; unlimited or unavailable allowances have no percentage bar.
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, or when you removed the threshold and put it back. A bar with no reset time is the exception: there, a threshold is rearmed once the percentage has dropped about ten points below it.
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?
Not from the interface. The default thresholds in Settings are chips to tick, 25, 50, 75, 90 and 100, and the right-click menu on a bell lists the same values. A value such as 60 or 85 written through the usageAlerts setting, by an agent for instance, still applies and shows up as an extra chip so you can turn it off.
Does this switch my account when the limit is reached?
Not by itself, and on purpose. An alert is what happens before the limit; moving the agent to another account is a quota rule, written in the same panel under Quota management: when the session reaches 99%, move the running agents. Alerts and rules read the same bars, and the account auto-switch page describes what the handover does.
I have two Claude subscriptions. Which one is the alert about?
The title says so. With one account the title is Claude · 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.
What is a quota rule, and what can it do besides warning me?
A rule watches any quota bar by default and acts on its own when the bar crosses a threshold. It lives in the Usage panel, in the Quota management block, and starts from one of five templates or from a blank rule: Use another provider (when any Claude gauge reaches 99%, new agents launch on Codex), Use a lighter model (at 90%, run new agents on a cheaper model or a lower reasoning effort), Use another account (redirect new launches to the spare account), Run a recovery trigger (start one of your triggers, once per window) and Alternate providers, which needs no threshold: new agents are shared in turn between Claude and Codex, or between two accounts, one launch out of two or a share of each quota. A blank rule also offers the actions Block a launch (every launch, or only scheduled agents, webhook calls or manual launches) and Move running agents (switch the agents already running to another account), and a condition can be limited to the last minutes before the window resets. Each rule names the provider, the account (a given one, or the most constrained), the window (any gauge, or the session, day, week or month), the threshold, and optionally a second condition on another window. Rules apply in the order you set, the first satisfied rule wins at launch, and each fires once per quota window. Redirections chain: if a rule sends a launch to a provider that has crossed a rule of its own, that rule applies in turn (Claude full, the launch goes to Codex; Codex full too, it goes to OpenCode), and a block at the end of the chain blocks the launch. An agent already running never changes CLI. A rule only blocks the launches of the provider it watches. Cursor and Antigravity can be watched too, with one gauge for the whole machine rather than one per account.
Does it also tell me when a quota I had used up is back?
Yes, since version 1.190. When a bar that had reached 90% or more resets, AgentsRoom announces it on the same channels as the threshold alerts, the in-app card, the desktop notification and the push to your phone, with the provider in the title (Claude quota reset) and a body such as You can code again: Current session is back to 3%, plus a short success sound unless notification sounds are off. A weekly bar that rolls over at 30% says nothing: the notice is for a quota you had actually used up. Turn it off with Tell me when a quota I had used up is reset, in Settings under Notifications, Usage alerts. A muted bar announces neither the thresholds nor the reset.
Can AgentsRoom start my Claude 5-hour window before I start working?
Yes, with Quota kick-off, a card in the same Usage panel. The countdown of a quota only starts with your first message; a kick-off sends that message for you, at times you set (07:00 on weekdays, for example) or back to back as soon as the quota refills, so the window you work in refills sooner. It covers the 5-hour sessions of Claude, Codex and Antigravity and the weekly limits of Codex and Antigravity. Claude's weekly limit is not listed because it refills on a fixed date no message can move, and neither are Grok, Kimi, Cursor, Copilot, OpenCode Go or Z.AI, whose periods are fixed or rolling. The feature was born from a user who typed a short hello by hand every morning to start his quotas.
Does a kick-off open an agent, and does it spend quota?
It opens neither an agent nor a tab: the account's own CLI runs in the background with one short message, then exits, and Claude and Codex keep no conversation of it. It is still one real request, sent to the cheapest model that draws from the quota (Haiku for a Claude session), so it costs a tiny share of that quota. Kick-offs fire while AgentsRoom is open; one missed while the computer was asleep or the app was closed leaves at the next opportunity if it is less than 6 hours late. A timetable in the panel shows every quota's window, the kick-offs to come and the refills they bring.
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 and Codex together
When a threshold should do something instead of notifying you: switch to Codex, change model, block launches, or alternate Claude and Codex one ticket out of two.
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.