# Quota Kick-off > The countdown of a Claude, Codex or Antigravity quota (a 5-hour session, a weekly limit) only starts with your first message, and the quota refills a fixed time after it. - Area: Desktop app - Plans: All plans - Last checked against the product: 2026-10-20 - Web page: https://agentsroom.dev/docs/quota-window-warmup ## What it does The countdown of a Claude, Codex or Antigravity quota (a 5-hour session, a weekly limit) only starts with your first message, and the quota refills a fixed time after it. Quota kick-off sends that first message for you, earlier: one line ("Reply with the single word: ok") to the cheapest model, through the account's own CLI, in the background, with no agent and no tab. Kicked off at 07:00, a 5-hour session refills at 12:00 instead of 14:00 if you start at 09:00. Per quota, you choose **Back to back** (the quota restarts the moment it refills) or **At set times** (for example 07:00 on weekdays). Requested by a user who sent a "hi" by hand every morning to start his quotas. **Video (1 min 11):** [Quota kick-off, shown in the real app](https://youtu.be/1NLtNobAWjo). The Usage panel's Quota kick-off card, the same day drawn with and without a kick-off, the Claude session set to kick off at 07:00 on weekdays, then a kick-off sent right now. ## Where to find it Footer **usage** badge > **Usage** panel > right-hand column > **Quota kick-off** card, right under **Quota management**. The card shows the next kick-off once one is set. **Set up** (or **Manage**) opens the **Quota kick-off** panel: a timetable with two sections, **5-hour sessions** (the next 24 hours) and **Weekly limits** (the next 8 days). Each quota is a lane: the window running now (solid, its elapsed part darker, its refill time at its end), the kick-offs to come (alarm-clock pins) and the refills they bring (dashed), the night hours shaded, a line for now. ## How to use it 1. Open the **Quota kick-off** panel. Read **How it works** once (the same day with and without a kick-off), then **Got it** folds it away; **How it works** brings it back. 2. Under a quota's lane, pick **Off**, **Back to back** or **At set times** (a weekly limit offers **Off** and **Back to back**: a kick-off leaves the moment the limit refills, day or night, so the next week and a 5-hour session start right away). 3. Picking **At set times** fills in a first slot right away: weekdays (Monday to Friday) at 07:00, the cheapest model; the pin and the dashed refill appear on the lane at once. Then tick the days (round initials, Monday first) and the times (up to six). On a 5-hour session lane you can also click the timeline to drop a kick-off at that time (snapped to the quarter hour), and click a pin to remove it (hovering the lane previews the time, "+ 06:30 PM"). A kick-off leaves at each time unless the quota is already running (then nothing is sent). A time already past when you set it is not owed for today. Below the settings, **A day with these times** replays a typical day, midnight to midnight: the sessions your times open ("Kick-off 09:00 AM, refills 02:00 PM"), the times skipped because a session already runs, and the rest of the day left to your first message. 4. **Model** defaults to **Cheapest (…)**: the cheapest model that draws from that quota (Haiku for a Claude session, the model of the group for a per-model weekly limit such as Fable, the CLI's own Gemini Flash for Antigravity's Gemini pool). Pick another one if you prefer. 5. The play button next to a quota's name (**Kick off now**) sends one message right away, whatever the lane shows. Under each lane, the status says what happened last ("Kicked off: 07:00", "07:00: already running, nothing sent", "Failed (07:00): the CLI refused the message", hover it for the CLI's own error) and what comes next ("Next kick-off: tomorrow 07:00", or for Back to back the refill time, "Kicks off as soon as it refills" when the quota is free now). The panel header sums it up ("2 on, next kick-off: tomorrow 07:00"). After a kick-off, AgentsRoom reads the provider's usage again so the lane shows the new window. **When a weekly limit is used up.** A used-up weekly limit (99 % or more) refuses every message until it refills, so a 5-hour session cannot start. While it lasts: - The lanes it covers say **Weekly limit reached, refills: 21:00** instead of "Ready", and a session lane shows a warning band from now to the refill. - Nothing is sent before the refill: no failed kick-off, no retries piling up. **Back to back** starts right at the refill (the dashed windows start there), and a set time held back leaves at the refill if it is less than 6 hours late; the pins it holds back are dimmed ("19:00: weekly limit reached"). - To kick off the moment the week refills whatever the session lane does, set the weekly limit's own lane (Weekly limits section) to **Back to back**: one message leaves a minute or two after the refill, even at night if AgentsRoom is open (asleep, it leaves at wake-up, up to 6 hours late). - **Kick off now** still sends when you ask, and the provider refuses it until the refill ("Failed: the CLI refused the message"). ## Settings - `quotaWarmup` (global, Usage panel > Quota kick-off): `{ entries: [...] }`, one entry per quota, keyed like the usage alert overrides (`||:`), with `mode` (`off` | `auto` = back to back | `schedule` = at set times), `days` (0 = Sunday), `times` (`HH:MM`, local), optional `model` (absent = the cheapest one) and `armedAt`. Default: empty, nothing is sent. Machine-local: it names this computer's account slots, and the computer holding the CLI session is the one that sends. - `wakeForTriggers` (global, Settings > Terminal > **Wake the machine for scheduled triggers**): also wakes the machine for the next set-time kick-off. Without it, a kick-off due while the computer sleeps leaves when it wakes up (up to 6 hours late); the panel says so while a set time exists. ## Agent tools (MCP) - `settings_get` / `settings_set` with key `quotaWarmup` read and write the whole configuration. - `usage_overview` shows the quotas and their reset times, which is how to check that a window started. ## Providers - Claude, Codex and Antigravity (per model group): the 5-hour sessions, whose countdown starts at the first message, and the weekly limits (Claude's per-model weekly limits too, such as Fable). - A weekly limit on **Back to back** is kicked off the moment it refills, whatever the provider shows next: Codex and Antigravity wait for a first message to start the next week, Claude can show the next week already counting, with nothing used. Either way the message starts a 5-hour session at the refill, and the week too when it waits for a first message. - Grok, Kimi, Cursor, Copilot, OpenCode Go and Z.AI are not listed: their periods are fixed or rolling, a message would start nothing. - A 5-hour session whose provider always publishes a reset time never reads free, so **Back to back** never sends anything there; **At set times** sends only when the quota shows nothing used. - Multi-account: each account's quotas get their own lanes, named after the account, and the message goes through that account's CLI home. ## Mobile Not on the mobile companion yet: the phone shows the gauges, the configuration is on the desktop that holds the CLI sessions. ## Limits - Sends only while AgentsRoom is open on this computer. A kick-off missed while asleep or closed is sent at the next opening if it is less than 6 hours late. - **Kick off now** on a quota that is already running still sends its line and says "Kicked off: