[{"data":1,"prerenderedAt":43},["ShallowReactive",2],{"doc:en:usage":3},{"title":4,"lede":5,"html":6,"headings":7},"Quotas and cost","The status bar, at the bottom of the window, shows how many agents are working, where the quotas of your Claude subscription stand and what you have spent today. This page explains what each figure means, where it comes from and what Escouade does when a quota nears its limit.","\u003Ch2 id=\"the-status-bar\">The status bar\u003C\u002Fh2>\n\u003Cp>The bar sits at the bottom of the window. From left to right:\u003C\u002Fp>\n\u003Cdiv class=\"table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Item\u003C\u002Fth>\n\u003Cth>What it shows\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>“3 active”\u003C\u002Ftd>\n\u003Ctd>The agents that are working, across all projects. Archived agents don’t count.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“1 waiting”\u003C\u002Ftd>\n\u003Ctd>The agents that are waiting for your answer. A click, or \u003Ccode class=\"key\">Ctrl+J\u003C\u002Fcode>, opens the next agent that is waiting or needs a look. As soon as there is one, the counter turns amber and its dot pulses.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“✓ 2 done”\u003C\u002Ftd>\n\u003Ctd>The agents whose task is done.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“4 Claude · 1.2 GB · 6% CPU”\u003C\u002Ftd>\n\u003Ctd>The running Claude processes, with the memory and processor they take. Missing when none runs. The tooltip lists each agent, the one using the most memory first.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Quotas\u003C\u002Ftd>\n\u003Ctd>The two quota windows of the current account: see the next section.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Today $4.12”\u003C\u002Ftd>\n\u003Ctd>What the agents have cost since midnight: see the “Cost” section.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“⎇ main ↑1 ↓3”\u003C\u002Ftd>\n\u003Ctd>The branch of the project on screen, when it is a git repository. A click opens the branch picker (\u003Ca href=\"\u002Fen\u002Fdocs\u002Fbranches\u002F\">branches\u003C\u002Fa>).\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>On the right\u003C\u002Ftd>\n\u003Ctd>The state of an \u003Ca href=\"\u002Fen\u002Fdocs\u002Fupdates\u002F\">update\u003C\u002Fa>, “♪ On” or “♪ Off” for the sound of \u003Ca href=\"\u002Fen\u002Fdocs\u002Fnotifications\u002F\">notifications\u003C\u002Fa>, and ⚙ for the settings (\u003Ccode class=\"key\">Ctrl+,\u003C\u002Fcode>).\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cdiv class=\"callout note\">\u003Cp class=\"callout-title\">Note\u003C\u002Fp>\u003Cp>On macOS, \u003Ccode class=\"key\">Ctrl\u003C\u002Fcode> becomes \u003Ccode class=\"key\">⌘\u003C\u002Fcode> in shortcuts (except \u003Ccode class=\"key\">Ctrl+Tab\u003C\u002Fcode>).\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"quotas\">Quotas\u003C\u002Fh2>\n\u003Ch3 id=\"reading-the-bars\">Reading the bars\u003C\u002Fh3>\n\u003Cp>Escouade follows the two quota windows of your Claude subscription: the 5-hour window and the weekly window. Each one is written compactly, a label, a bar and a countdown:\u003C\u002Fp>\n\u003Cp>\u003Ccode>5h … reset 3h01 | W … reset 4d 12h\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>“5h” is the 5-hour window, “W” the weekly window (7 days).\u003C\u002Fli>\n\u003Cli>The bar fills with the share of the quota used. It turns amber above 80%.\u003C\u002Fli>\n\u003Cli>“reset 3h01” is the time left before the window resets: 3 hours and 1 minute. From one day on, the countdown reads “4d 12h”. The word “reset” is the same in both languages.\u003C\u002Fli>\n\u003Cli>The percentage isn’t written: it shows when you hover the label, the bar or the countdown, with the date of the reset. For example: “42% · resets on 10\u002F10 at 6:00 PM”.\u003C\u002Fli>\n\u003Cli>With a single account, \u003Ccode class=\"key\">Tab\u003C\u002Fcode> focuses each bar, which screen readers announce as “5-hour quota” or “7-day quota” with the same value.\u003C\u002Fli>\n\u003Cli>As long as Escouade has read nothing, the bar is empty, a “—” replaces the countdown and the tooltip says “Quota unavailable”.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3 id=\"with-several-accounts\">With several accounts\u003C\u002Fh3>\n\u003Cp>As soon as there is more than one account in \u003Ca href=\"\u002Fen\u002Fdocs\u002Faccounts\u002F\">the list of accounts\u003C\u002Fa>, the bar writes the current account’s name in front of the two quotas: it is the account a new agent would start on right now, leaving out the accounts reserved to projects.\u003C\u002Fp>\n\u003Cp>The group then becomes a button, “Quota by account (current account: Pro)”. A click (or \u003Ccode class=\"key\">Enter\u003C\u002Fcode> with the keyboard) opens the “Claude accounts quota” panel above the bar. \u003Ccode class=\"key\">Esc\u003C\u002Fcode> or a click outside closes it. It shows each account, the current one first, then the others in the order of the settings:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>its name, with the “current” tag for the current account and “past the pause threshold” when one of its windows has passed “Pause above quota”;\u003C\u002Fli>\n\u003Cli>what its turns cost today, for example “Today: $1.20” (with “≈” while a turn is running);\u003C\u002Fli>\n\u003Cli>its two windows, this time with the percentage written next to the bar;\u003C\u002Fli>\n\u003Cli>dimmed, the reason when the account isn’t fully read: “Inactive”, “Not signed in”, “Sign-in expired: run Claude Code again for this account.”.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3 id=\"where-the-quotas-come-from\">Where the quotas come from\u003C\u002Fh3>\n\u003Cp>Escouade reads each account’s quotas again every minute, a first time two seconds after startup. The figures come from two sources:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>A Claude process of the account\u003C\u002Fstrong>, when an agent of the account is running: Escouade queries it, and Claude Code also reports the state of the windows by itself during a turn. It is the most direct source.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Anthropic’s usage service\u003C\u002Fstrong>, for an active account no agent is running on. Escouade queries it with the sign-in Claude Code keeps for the account, which it reads without changing, and at most once every 5 minutes per account. The request goes through the proxy of the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-network\u002F\">network settings\u003C\u002Fa> if there is one.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>When an account has just been signed in, its quota is read right away.\u003C\u002Fp>\n\u003Ch3 id=\"when-a-quota-isn-t-read\">When a quota isn’t read\u003C\u002Fh3>\n\u003Cdiv class=\"table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>What you see\u003C\u002Fth>\n\u003Cth>What it means\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>“Quota unavailable”, empty bar, “—”\u003C\u002Ftd>\n\u003Ctd>Escouade hasn’t read anything for this account yet, or the reading failed.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Not signed in”\u003C\u002Ftd>\n\u003Ctd>Escouade finds no claude.ai sign-in for this account. Sign it in from \u003Ca href=\"\u002Fen\u002Fdocs\u002Faccounts\u002F\">the accounts\u003C\u002Fa>. For Main: “Not signed in with a claude.ai account (API key?)”.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Sign-in expired: run Claude Code again for this account.”\u003C\u002Ftd>\n\u003Ctd>The sign-in is out of date. Claude Code gets a new one when it runs; “Sign in…” in the accounts settings renews it.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Inactive”\u003C\u002Ftd>\n\u003Ctd>The account is switched off. Its quota is only read through an agent running on it.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Figures that no longer move\u003C\u002Ftd>\n\u003Ctd>A reading that fails (network, server, proxy) leaves the last values in place.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>For an account that is “Not signed in” or whose sign-in has expired, the last values read stay shown until the end of their window.\u003C\u002Fp>\n\u003Cdiv class=\"callout note\">\u003Cp class=\"callout-title\">Note\u003C\u002Fp>\u003Cp>On macOS, Claude Code keeps the sign-in in the keychain, and macOS may ask you to allow Escouade to read it. If you refuse, Escouade doesn’t ask again for 10 minutes.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"cost\">Cost\u003C\u002Fh2>\n\u003Cp>Amounts are in US dollars.\u003C\u002Fp>\n\u003Ch3 id=\"today\">Today\u003C\u002Fh3>\n\u003Cp>“Today” is the sum of the turns finished since midnight, your computer’s time, across all accounts, including those you have removed since. It updates at the end of each turn. With several accounts, the quota panel gives the same total account by account.\u003C\u002Fp>\n\u003Ch3 id=\"live-during-a-turn\">Live during a turn\u003C\u002Fh3>\n\u003Cp>While Claude works, tokens and cost rise live. Claude Code only gives a turn’s exact cost when it ends; until then, Escouade estimates it from the models’ public prices (input, output, cache read and cache write). An estimate is written with “≈” in front of the amount, and the tooltip explains it: “Estimate (public prices) while Claude works; exact cost at the end of the turn”.\u003C\u002Fp>\n\u003Cp>When the turn ends, Claude Code’s exact figure replaces the estimate. For a model whose price Escouade doesn’t know, tokens rise but the cost only appears at the end of the turn.\u003C\u002Fp>\n\u003Ch3 id=\"where-to-see-an-agent-s-figures\">Where to see an agent’s figures\u003C\u002Fh3>\n\u003Cdiv class=\"table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Where\u003C\u002Fth>\n\u003Cth>What is shown\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>The agent’s card, in the sidebar\u003C\u002Ftd>\n\u003Ctd>Its tokens (“tok”), its cost and the number of modified files.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>The conversation header\u003C\u002Ftd>\n\u003Ctd>“Tokens” and “Cost”, with “Context” and “Duration”.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>End of a turn\u003C\u002Ftd>\n\u003Ctd>The “Task done” card (duration, tokens, cost, edited files), or a duration · tokens · cost line between two turns.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>A Kanban ticket’s card\u003C\u002Ftd>\n\u003Ctd>Its agent’s cost.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ca href=\"\u002Fen\u002Fdocs\u002Foverview\u002F\">Overview\u003C\u002Fa>\u003C\u002Ftd>\n\u003Ctd>Each agent’s cost.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>The \u003Ca href=\"\u002Fen\u002Fdocs\u002Fstats\u002F\">statistics\u003C\u002Fa> add all this up by day, week or month.\u003C\u002Fp>\n\u003Ch2 id=\"when-a-quota-nears-its-limit\">When a quota nears its limit\u003C\u002Fh2>\n\u003Cp>Escouade reacts in three ways. The first two depend on the “Pause above quota” threshold, which you set in Settings › Kanban, “Autopilot” group: 80, 90, 95 or 100% of a window, 100% by default, the same for all projects (\u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-board\u002F\">the Kanban settings\u003C\u002Fa>). An account is at the threshold when one of its windows reaches it and its reset is still to come.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>New agents change account.\u003C\u002Fstrong> When the current account passes the threshold and another one is available, new agents and tickets start on the other. A notification says so: “The Main account has reached 91%: new agents now go to Pro.” (\u003Ca href=\"\u002Fen\u002Fdocs\u002Faccounts\u002F\">Several Claude accounts\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The autopilot pauses.\u003C\u002Fstrong> When every account a ticket can use is at the threshold, no ticket starts. The Kanban then writes, under its header, a line such as “Autopilot paused: 5-hour quota at 92% (resumes at 3:00 PM)”, with the names of the accounts concerned when there are several, and the “Resume now” button to override it. The pause lifts by itself at the reset. When a ticket’s agent hits the usage limit with no resume planned (auto-resume off, or the reset time unknown), no ticket starts either for 30 minutes on its account. See \u003Ca href=\"\u002Fen\u002Fdocs\u002Fautopilot\u002F\">the autopilot\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>An agent reaches the limit mid-turn.\u003C\u002Fstrong> It stops and resumes by itself after the reset, or on another account if you ask for it. See \u003Ca href=\"\u002Fen\u002Fdocs\u002Faccounts\u002F#resume-an-agent-stopped-by-the-usage-limit\">Resume an agent stopped by the usage limit\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Fol>\n",[8,12,15,19,22,25,28,31,34,37,40],{"id":9,"text":10,"depth":11},"the-status-bar","The status bar",2,{"id":13,"text":14,"depth":11},"quotas","Quotas",{"id":16,"text":17,"depth":18},"reading-the-bars","Reading the bars",3,{"id":20,"text":21,"depth":18},"with-several-accounts","With several accounts",{"id":23,"text":24,"depth":18},"where-the-quotas-come-from","Where the quotas come from",{"id":26,"text":27,"depth":18},"when-a-quota-isn-t-read","When a quota isn’t read",{"id":29,"text":30,"depth":11},"cost","Cost",{"id":32,"text":33,"depth":18},"today","Today",{"id":35,"text":36,"depth":18},"live-during-a-turn","Live during a turn",{"id":38,"text":39,"depth":18},"where-to-see-an-agent-s-figures","Where to see an agent’s figures",{"id":41,"text":42,"depth":11},"when-a-quota-nears-its-limit","When a quota nears its limit",1791926756497]