Accounts and plan usage
The Accounts view keeps your agent CLI and browser accounts in one place, records how much of each plan’s limits you have used, and can pick an account for each new session or request. Plan usage comes from what each provider reports. It is separate from the estimated API spend in Stats.
- App
- Accounts
- CLI
hansard account
Manage accounts in the app
Section titled “Manage accounts in the app”

- Select Accounts in the dock. Overview shows every account’s limits on a board, or their resets on a timeline, and what each agent uses now. The rail lists each saved and detected account. Select an account in the rail or on the board to open its page.
- To add an account, select Add account and choose a service.
- Enter an Account name and sign in:
- For Codex and Claude Code, Sign in and connect starts the local router and opens provider authorization in your browser. Sign in once, then choose the routing mode and select Enable or Save. The account is already connected, so routing does not require another login. Existing routing rules and selections are retained. Restart the coding tool after enabling.
- For isolated Codex or Claude Code settings and conversation storage, select Use a separate CLI profile. Native profiles have their own sign-in, separate from the router. To register a profile folder you already have, select Use an existing profile and enter its Profile directory.
- If the provider shows an authorization code, or the browser can’t return to Hansard, paste the code or the page’s address into Authorization code or callback URL in the same step, then select Finish authorization.
- To finish a Codex sign-in on another computer or phone, select Use a code instead. Open the page it shows in any browser and enter the code. The account connects as soon as the code is approved.
- For native profiles, sign-in opens the official CLI flow inside Hansard. Cursor CLI offers Sign in with browser and Sign in on another device. The latter shows the native sign-in link with Copy link and opens no browser. Open the copied link on the device where you want to authorize the login.
- Devin offers Sign in with browser and Paste a token. For a token, open Devin’s sign-in link and paste its token when the field becomes available. Select Submit token. Hansard clears the field and sends the token to Devin’s own prompt without saving it. Devin owns the resulting credential. When sign-in finishes, Hansard checks the account and its reported usage.
- For ChatGPT, Claude.ai, Cursor, Devin, and Grok on the web, Hansard opens a separate Chrome or Edge profile. Sign in once in that window.
- For Antigravity, register the device’s existing sign-in. Separate saved
sign-ins are unavailable: agy keeps one Google sign-in for each computer
user in the operating system keyring, and the Antigravity app and editor
share it. agy signs in with that account first. To use another account,
type
/logoutand then/loginin agy./logoutalso signs the app and editor out. While Antigravity routing is on, a login that no Google account holds yet also offers Sign in through the router. It opens Google’s sign-in page in the browser and leaves the keyring sign-in as it is. The new router account takes the login’s name and replaces the login.
- An account’s page starts with its Plan, then its Limits, each with
the time until it resets, then its resets, limit history, and use. Its
Sign-in section lists each app and router copy that signs in as the
account. A sign-in that needs a next step shows a button for it, and the
More actions menu beside it holds the rest:
- Sign in or Fix sign-in appears first when the account needs it.
- Sign-in refused means the last sign-in used a different account, so the saved login kept its earlier sign-in. The sign-in offers Sign in again and, for an account not saved yet, Add as a new account.
- Open ChatGPT, Open Claude.ai, and similar buttons open a browser account.
- New session opens the CLI in Terminal with that account.
- Check connection checks the sign-in and usage now.
- Manage renames the account, pauses it, signs in again, or removes it.
Keep the sign-in dialog open until the account appears. If authorization has finished and the router is busy updating accounts, Hansard retries the connection without another sign-in. A failed authorization identifies the stage when the router reports it, such as a callback timeout or an unsuccessful code exchange. You can start another sign-in while one is still open: each finishes with its own account name, and canceling one leaves the others running. A code is valid for 15 minutes. When a sign-in ends without connecting, select Get a new code or Start again in the same dialog.
To pause a native account, clear Include in capture and routing in Manage. A paused account is left out of automatic capture, routing, and new launches. Remove account removes it from the list but keeps its provider login files and usage history. Router accounts use Include in routing; removing a router account removes that router login.
To retire an account you no longer use, choose Retire account… in its
More actions menu. Hansard stops routing to it and checking its usage,
removes its router sign-in, and pauses its saved logins, but keeps its usage
history. Accounts lists it under Retired, where Restore resumes its
saved logins; routing it again needs a new sign-in. From the CLI, run
hansard account retire <account> and hansard account restore <account>.
Each account shows the plan the provider reports, or Plan unknown. The Sign-in section ends with the account’s workspace or organization ID, and Manage shows the full identity and connection details. Custom account names never replace the provider’s email, username, or team.
Each account has one name. Renaming it in Manage or with
hansard account rename also names its saved logins and its router sign-ins,
and a name a login reports never replaces the name you gave.
Rename in the More actions menu at the top of an account’s page also renames it. Sign-in lists each native sign-in and router login with its state and actions, and its Copy button copies the workspace ID.
Sign-in history, below Sign-in, lists retained sign-in events on this
computer. Different accounts and workspaces use separate sign-in folders.
Usage checks repair earlier shared folders, and Sign-in names any sign-in
needed afterward. hansard account status reports the current state from a
terminal.
Personal Sync carries names you set only when it can verify the same account membership on another device. Different workspaces keep separate names. Names without verified membership stay local. Credentials and sign-in folders never travel with those names.
Link chat account… links a ChatGPT, Claude.ai, Gemini, NotebookLM, Grok, Kimi, or Meta AI chat account to the account’s name. Hansard suggests a link only when exactly one account from the same company has a matching email. Select Link or Not now. Hansard never links automatically. The link stays on this device, while Personal Sync carries the chat account’s new name.
With Personal Sync, accounts used on another device in the past 30 days appear below this device’s accounts when they are not set up here. Set up here starts sign-in for that provider and identifies the account to select. Credentials never travel through Personal Sync. Each device signs in separately.
Account groups follow Settings → Appearance → Harness order, as the session browser does. Within an email group, reported plans sort from highest tier to lowest. Unknown plans stay explicit, and unverified device captures appear separately. A custom name never replaces a provider identity.
Manage accounts from the CLI
Section titled “Manage accounts from the CLI”hansard account add personal --provider codexhansard account login personalhansard account add work --provider claude --home ~/.claude-workhansard account capturehansard account run personaladdcreates an isolated profile forcodex,claude,grok,devin,cursor, ormuse. With--home, it registers an existing profile folder instead. Each profile has its own provider settings, skills, and conversation history. A Cursor CLI profile keeps its login in the CLI’s file credential store inside the profile; on macOS the profile is also the session’sHOME, so shell startup files and git configuration come from the profile.loginruns the provider’s official sign-in and keeps it only when it signs in to the account the saved login belongs to. Terminal names that account before the sign-in starts. A sign-in to another account fails with a message that names both accounts, for example “You signed in as Personal, but this saved account is Work. Sign in with Work, or add Personal as a new account.” The saved login keeps working with its earlier sign-in. A sign-in to a workspace another saved account already holds, or one Hansard cannot verify, is not kept either. A saved account with no verified account yet accepts any account. Login tokens never move between profiles.login --device-codesigns Codex or Grok Build in with a code instead of a browser on this computer: Terminal shows a page and a code to enter in a browser on any computer, for example when connected over SSH. The same account check applies. Muse Code uses a code for both login forms. Its profile uses file credentials inmuse/auth.jsonbeneath an isolated XDG configuration root. Hansard checks the native account email and allowance before keeping the sign-in. An existing Muse profile supplied with--homemust use file credentials. Hansard does not copy a Muse Keychain login.login --browser-linkruns Cursor CLI withNO_OPEN_BROWSER=1, so it prints the sign-in link without opening a browser. Accounts provides the same method through Sign in on another device and Copy link.login --manual-tokenruns Devin’s native pasted-token flow. Accounts provides the same method through Paste a token. Hansard sends the token only to the CLI prompt and does not save it. Both alternate methods retain the account identity check and require a person to sign in.runstarts a new CLI process with that account. Pass provider arguments after--, for examplehansard account run personal -- exec "Explain the test layout". Running apps and sessions keep their accounts.capturechecks usage for every enabled account, or for one account when you name it.list,rename,enable,disable, andremovemanage saved accounts.renamenames the whole account, including its router sign-ins.removekeeps credentials and archived history.
For ChatGPT and Claude.ai, save browser profiles and open them from the CLI:
hansard account add chat-personal --provider chatgpthansard account add claude-work --provider claude-web --browser edgehansard account open chat-personalBrowser providers are chatgpt, claude-web, cursor-web, devin-web, and
grok-web. --home registers an existing browser user data folder, and
--browser-profile "Profile 1" selects a profile inside it.
Hansard imports and watches the history of every registered profile, including
paused ones. Removing an account stops that discovery and keeps what is already
archived. Profiles that Hansard creates live in Hansard’s home folder:
hansard update keeps them, but hansard reset and uninstalling without
--keep-data delete them, including their credentials and history. Move a
profile outside Hansard’s home folder first to keep it.
Run hansard help account for every subcommand and flag.
For Amazon Bedrock, Vertex AI, or OpenRouter, use Cloud model connections. Saving a cloud connection does not activate it. API billing starts only after selection and use, with no automatic fallback from subscriptions.
Track plan usage
Section titled “Track plan usage”- In Accounts, select Check now in the header. On Overview it checks every enabled account, and on an account’s page it checks that account.
- To keep checking, turn on Track plan usage in the header. The watcher then samples plan limits every 15 minutes while it runs and your Mac is awake. The header shows when the last check finished.
- Select an account in the rail or on the board to open its page.
The rail lists accounts in the same order and groups as the session browser. An account’s page shows its Plan first: plan details, spend control, extra credits, Resets available, and each reset grant. Limits follows, with every limit of the latest check on one line, then the resets and one chart of a limit’s captured history over up to 30 days, with a picker when the account has several limits. Depending on the provider, the page can also show Spending, Share of usage this week by product, the sessions that used the account, Activity, Daily tokens, and Longest turn. A plan without a five-hour limit, such as some Claude and Codex plans, lists only the limits it has. Accounts you no longer use stay listed with their history.
Under Limits, each limit with recent checks shows where its pace leads: At this pace, lasts until it resets, or At this pace, runs out around a named time. The pace extends the provider’s own reported percentages over the last 90 minutes for short limits and up to a day for weekly ones. Codex, Claude Code, and Grok Build accounts also list the sessions that spent that provider’s use over its shortest limit, ranked by their recorded tokens at API prices. When every account of a provider on this device is at a limit, or reaches one within two hours at its current pace, an alert at the top of the window names when it runs out. It shows once for running out and once for reaching the limit, until the provider’s first limit resets.
To turn tracking on or off from the CLI:
hansard config setup --track-usagehansard config setup --no-track-usageTo estimate what each Claude and Codex plan is worth at API prices from this
history, open Subscription value in Stats or run hansard account value.
See Estimate what a plan is worth.
How capture works:
- Up to four accounts are checked at once. Capturing usage never sends a model prompt and never redeems a reset.
- A reset is used only when you press Use reset and confirm. On a Codex
account, Hansard sends the request the Codex client sends, then checks the
account again. Claude has four kinds of reset, and each one says which limit
it resets: a full reset resets your plan’s 5-hour and weekly limits, a 5-hour
or weekly reset resets that limit, and a Fable reset resets only your Fable
limit and gives back to your weekly limit what Fable used this week. On a
Claude account the button names the kind, such as Use Fable reset, and
appears only while Claude Code reports its
/limit-resetcommand switched on for that account. Confirming opens Claude Code in Terminal with that command for the kind you chose, and Claude Code asks again and sends the request; Hansard never sends it.hansard account limit-reset [--kind fable|full|5-hour|weekly]opens the same Claude Code command for a saved Claude login, or for the default login without a name. Other Claude resets open claude.ai Settings > Usage for the account, with one line when Claude Code has the command switched off. - Claude reports some accounts’ resets only inside Claude Code. For those,
Accounts says so and offers Open Claude Code, which opens Claude Code in
Terminal for that account with no command; run
/limit-resetthere to see your resets.hansard account limit-reset --opendoes the same. When Claude Code has already checked the account, Accounts also shows whether it found an unused reset. - Codex and Claude checks use the account’s saved sign-in for read-only usage requests. If the saved sign-in cannot be used, the official client handles the check.
- Each provider membership keeps its own history. Several profiles for the same membership share one history.
- A failed check keeps the last successful values and their original time.
- Hansard keeps up to 32 saved connections and 64 usage accounts.
- Providers whose CLI is not installed are skipped without errors, and their saved accounts stay visible. On macOS, Codex capture also finds the CLI bundled with Codex.app or ChatGPT.app.
- Hansard cannot fill in time it did not observe. A blank stretch after sleep, or while the watcher was off, means no data, not zero use.
What each provider reports:
- The Codex usage read covers only the active ChatGPT workspace. If one login has personal and business workspaces, select each workspace in Codex and capture it once. Claude organizations and Devin and Grok Build team workspaces work the same way.
- Claude reports model-specific limits, usage-credit spending and caps, subscription and seat details, reset eligibility, and weekly usage by product.
- Codex reports reset allowances and expiry, credit controls, daily token totals, the longest turn, lifetime and peak daily tokens, and streaks. For a Team, Business, Edu, or Enterprise workspace it also reports the workspace name and your role, from the workspace list the Codex CLI checks before each turn.
- Antigravity reports the Google AI plan its CLI shows beside the signed-in account, and a router account reports the same plan from Google’s account check, or Free for an account without one. Grok Build reports the subscription tier its CLI keeps for the signed-in account. When either is missing, the plan shows as unknown. Grok Build reports plans of The X Subscription under the older SuperGrok tiers, so Hansard shows them by their X Subscription names: Premium, Super, and Ultra. A SuperGrok, SuperGrok Plus, or SuperGrok Heavy plan kept from before The X Subscription reports the same tier and shows the same name. SuperGrok Lite and X Premium plans keep their own names.
- Cursor reports the plan, the share of the billing period’s included usage
used, and the on-demand spending cap, as the Cursor CLI’s
/usagepanel shows them. Pro, Pro+, Ultra, and Teams plans split included usage into two pools, named as Cursor names them: Cursor Models (Composer and Cursor’s Grok models) and Other Models (named third-party models). The account’s card shows one pool on each line, and its page charts the total and both pools. Hobby and Start plans have the Cursor Models pool alone, and a plan whose included usage resets weekly shows one weekly limit. Enterprise members report their personal spend for the billing period instead. Hansard reads them with the Cursor CLI’s saved sign-in and the Cursor app’s sign-in on this device; when both are the same Cursor user, they show as one account. A Cursor browser profile is a separate sign-in whose plan Hansard cannot read. - Resets available counts provider-granted resets, including zero. Claude separates remaining grants from resets usable now. An account that is not eligible lists quota resets as Unavailable; an unreachable endpoint never shows as zero. Provider-granted resets, scheduled window resets, and the completed cycles Hansard observes are tracked separately.
Claude Code reports usage-credit spending for Pro, Max, Team, and Enterprise
accounts when its /usage output includes it. Team and Enterprise figures
describe your own membership, not the organization budget. Team member rows
need Claude Code 2.1.236 or newer. Spending keeps zero, unlimited,
disabled, and unreported limits distinct; a missing row does not mean zero.
Organization owners can see shared usage-credit budgets in Claude’s
organization usage settings. The estimated spend in Stats is not billing spend
and never appears here.
Provider commands report different scopes:
| Command | Shows | Scope |
|---|---|---|
Claude /usage (aliases /cost, /stats) |
Live limits and spending, plus local activity | Limits are account-wide; activity is this machine only |
Claude /usage-credits |
Billing settings, or a request to an administrator | Account or organization action |
Claude /status, /context |
Sign-in, configuration, and current context use | The current CLI process and conversation |
Codex /usage daily|weekly|cumulative |
Token activity from the account service | The signed-in account |
Codex /status |
Session configuration and token use | The current conversation |
Claude’s skill, subagent, plugin, MCP, loop, and cache breakdowns come from local sessions, so Hansard does not assign them to whichever account happens to be signed in. Organization-wide analytics need a separate reporting connection. See Anthropic’s command reference, usage and cost guide, and limit resets, and OpenAI’s account usage protocol.
Account records, provider profiles, and routing choices stay on this device. With Personal Sync, your captured usage history also appears on your other devices.
API key accounts
Section titled “API key accounts”API key accounts route model requests with provider billing. They are separate from ChatGPT, Claude, and other subscription logins.
| Provider | Routed coding tool |
|---|---|
| OpenAI | Codex |
| Anthropic | Claude Code |
| Google Gemini | Antigravity CLI |
| xAI | Grok Build |
- Open Accounts > Add account > API key account.
- Select the provider.
- Enter an account name.
- Enter the API key.
- Under Projects, choose organizations, projects, or portfolios. Select Add folders to enter absolute folder paths.
- Set optional daily and calendar-month USD caps.
- Select Check key and save.
- On the key’s page, turn on Allow API key spending.
Hansard checks the provider’s model list before saving a key, and a key serves the models on that list. The router reads the list again with the saved key when a request names a model the list lacks, at most once in ten minutes for a key, and once a day, so a model the provider releases later needs no action. Check models in the More actions menu on the key’s page reads it at once. A read changes the list only: spending, caps, and project rules stay as saved. Hansard stores the key in an owner-only local file, outside Personal Sync and Teams. A new key starts with spending off, and replacing a key turns spending off until it is allowed again. Saving updates existing recorded routing integrations. Restart connected coding tools to apply the address. If the tool is not connected, start the local router under Routing. The key’s page shows today’s and this month’s spend against each cap. Its Used by section shows whether Hansard routes the tool and offers the button named for it, such as Configure Claude Code, when it does not. Routing that does not use the saved settings yet shows Apply routing at the top of the page. Turning off Allow API key spending stops routing to a key without removing it.
A selected project uses the key before the ordinary subscription pool and its rules. An organization rule covers every project in that organization. Failures and caps fall back to that pool. A key with no project rules is a fallback instead: it serves a request only when no subscription account can, for example when every account has reached its limit. Use only this key in these projects blocks fallback in identified matching projects. Several keys can have this setting for one project: the project then uses those keys only, the ones that are on and under their caps in turn, and no other account. Unknown projects never use a project-limited key. A new session may use the ordinary pool until Hansard records its folder. Claude Code and Codex supply session IDs for this lookup. A harness request without a resolvable local session ID uses the ordinary pool. Folder rules include descendants after resolving symbolic links.
Caps use Hansard’s estimate from requests it routed, not the provider’s bill. They reset at midnight UTC and the first day of each calendar month UTC. Accounts show a notice at 80% and withhold the key at the cap. One admitted request can finish above a cap. Capped keys admit one request at a time until usage settles. Unpriced models, unsupported service tiers, and incomplete usage withhold capped keys. An interrupted request can keep a hold until the period resets. Replacing a key retains its account’s spend. Removing an account removes its saved credential.
Resolved sessions keep their selected key or ordinary pool until it fails, reaches its cap, loses eligibility, or the gateway restarts. Bindings expire after one idle hour. The gateway supports HTTP and event streams. A gateway interruption requires a retry after the supervised router worker recovers. Hansard never replays a request after output begins. With no API key accounts, client setup uses the direct router address.
The CLI provides the same account actions. Use an owner-only file for the key:
hansard account api-key save Work --provider claude --key-file /private/path/key \ --daily 5 --monthly 80 --projects example-project \ --credit-for account_<subscription-id> --credit 100 --renews 7hansard account api-key configure claudehansard account api-key listhansard account api-key save Work --id <account-id> --only truehansard account api-key save Evals --id <account-id> --reserved true \ --reserved-label "Evals and benchmarks"hansard account api-key remove <account-id>Use --daily none or --monthly none to clear a cap. Use --projects none,
--portfolios none, or --folders none to clear selectors. Project and portfolio
IDs come from hansard projects list. hansard account api-key apply retries
applying saved accounts after the router starts.
hansard account api-key requests lists the requests to xAI models that
Hansard routed, newest first, with the server-side tools xAI reported running
for each, such as x_search and web_search calls, and their totals. Pass
--session with a Grok Build session ID to see one conversation, for example
to check that an answer made an X search.
Use --credit-for, --credit, and --renews together to link a key to an
Accounts subscription account. Accounts shows the monthly amount you enter,
routed spend in the current renewal cycle, the amount left, and the next
renewal date at UTC midnight. Days beyond a month’s end use that month’s last day.
This is the key’s routed estimate on this device, not the provider balance.
Other keys and devices can spend the same grant. Unknown usage leaves the
remaining amount unknown. The credit amount does not set a spend cap.
Choose the subscription in Manage > Subscription credit, or pass its stable
Accounts ID or unique name. Set all three flags to none to remove the link.
Hansard warns when the linked provider or client is outside the
credit coverage. OpenAI API credits do not cover Codex CLI requests made with
an OpenAI API key. The amounts are not built into routing code because plans
change. Terms checked 2026-10-30:
- Anthropic
grants Max $100, Ultra $200, and Team up to $500 monthly, pooled.
Eligible API and Agent SDK usage includes
claude -pwith the linked organization’s API key. Interactive Claude Code is excluded. - OpenAI grants Pro 100, Pro 200, and Pro 500 $100, $200, or $500 by tier and Business up to $500 pooled monthly. API-key Codex usage is excluded. Annually prepaid Business grants are annual and do not fit this monthly estimate.
Unused credits expire each billing cycle. Claim the benefit in provider billing before entering its amount in Hansard.
Use --reserved true to keep a key out of ordinary automatic routing. Give the
key’s hskey-<id>/<model> model prefix, X-Hansard-Api-Key-Account header, or
hansard account run <key-account> -- <command> [arguments] launch to select it. A
matching project or folder rule also selects a Reserved key. Daily and monthly
caps and project restrictions still apply to explicit requests. Replace key_
in the account ID with hskey- to build its prefix. The header accepts the
account ID, prefix, or unique name and requires gateway client authentication.
Direct router prefixes cannot spend a key without the gateway’s private ticket.
Launches supply temporary local API endpoints without changing saved provider
configuration. Benchmark commands can use the standard provider API environment
variables or HANSARD_API_KEY_BASE_URL and HANSARD_API_KEY_TOKEN. The token is
for the local relay, not the provider key. The relay closes when the command exits.
Update every routing device before relying on synced reservations. Older
installations cannot apply the new metadata and can retain earlier local rules.
Rotate router client keys
Section titled “Rotate router client keys”The router’s client keys authenticate coding tools to the local router. They are separate from provider API keys and provider sign-ins.
- Start the router with the updated Hansard version.
- In Accounts > Routing > Local router > Client keys, select Rotate.
- Set the grace period.
- Select Rotate in the dialog.
- Restart existing clients before the displayed retirement date.
The default grace period is 24 hours. The maximum is 7 days. Durations use s,
m, h, or d. Both generations work during grace. Use 0s to retire the old
keys immediately. A restart preserves the retirement dates. Rotating again does
not extend an earlier grace period.
Hansard updates recorded routing settings and new launch environments for its supported clients. It preserves unrelated preferences and reports conflicting settings. Resolve a reported conflict before reconnecting that client. Existing processes keep their original launch environment until they restart.
The router shows when old keys stop working and how many distinct sessions used them in the past hour. Requests without a session identity cannot contribute to this count. The count comes from local request records and contains no key value.
The same operation is available in the CLI:
hansard account proxy rotate-keyhansard account proxy rotate-key --grace 30mhansard account proxy statusRotation replaces the direct router key, the API key gateway’s private token and surrogate credentials, and the Muse gateway key. Provider credentials stay unchanged. Client keys use owner-only storage on this device. Personal Sync and Teams never carry them. Commands and the viewer never display key values.
Connect usage APIs
Section titled “Connect usage APIs”Read-only usage APIs add Cursor team spending, Claude Enterprise member caps, Factory credits, and GitHub Copilot billing. These connections never route model requests. Use API key account for an ordinary inference key.
- In Accounts, select Add account, then Usage reporting connection.
- Select the provider, enter the account selector and an API key with read access, and select Connect and check usage.
- To rename the connection, replace its key, or disconnect it, select Manage on its card. Earlier usage history stays available.
Hansard saves keys entered here in private local files, outside the archive and sync. Cursor personal usage comes from the Cursor CLI and app sign-ins on this device; the usage APIs add team and organization figures.
To configure connections in a file instead, add usage.connections to the
file printed by hansard config path:
{ "usage": { "connections": [ { "id": "cursor-workspace", "type": "cursor-member", "label": "Example workspace", "email": "user@example.com", "tokenFile": "~/.config/hansard/secrets/cursor-readonly" } ] }}Merge this with your existing configuration, then select Check now. Each
entry needs a stable, unique id, a type, and either tokenFile (a file that
contains only the key, readable by your user) or tokenEnv (the name of an
environment variable available to the app and the watcher). label sets a
custom name. Keep the same id across devices and key rotations. Up to ten API
connections are checked alongside the installed CLIs.
| Type | Account selector | Access needed and what it captures |
|---|---|---|
cursor-member |
email |
Team Admin API key. On-demand spend and the member’s enforced cap. |
cursor-organization |
organizationId |
Organization API key. Contract pool used and limit. |
claude-enterprise |
userId |
Organization owner-issued admin key starting sk-ant-admin, with read:spend_limits. The Enterprise member’s inherited cap and spend. Ordinary Anthropic API keys are refused. |
factory-member |
None | Enterprise Analytics enabled. Members can read their own credits. |
factory-organization |
None | Analytics access with the Manager or Owner role. Organization credits. |
copilot-user |
username |
GitHub token with Plan read permission. AI credits and billable usage. |
copilot-organization |
organization, optional budgetId |
GitHub token with Administration read permission. Usage and the organization’s AI-credit hard budget. |
Factory reports credits, not dollars, through yesterday UTC; on the first of the month it shows the previous month. Copilot caps appear only when the selected budget is a hard AI-credit budget for the organization. The public Cursor APIs cover teams and organizations; individual subscriptions report through the Cursor sign-ins on this device instead. A missing permission appears as a notice and never overwrites saved values with zeros. See the provider documentation: Cursor Team API, Cursor Organization API, Claude Enterprise API, Factory Analytics, GitHub usage, and GitHub budgets.
Choose an account for each new session
Section titled “Choose an account for each new session”An account pool picks a Codex, Claude Code, Grok Build, Devin, or Cursor CLI account each time you start a CLI session. It balances session starts, not token volume.
- Open the Routing tab. Under Session launch rules, select Create pool.
- Enter a Pool name, choose the Service, and choose a Selection policy: Use in order, Spread new sessions, or Most quota remaining.
- Select the accounts and move them up or down to set their order.
- Optional: in Quota rules, set how much quota to keep in reserve and how old a usage check can be.
- Select Save pool. To start a session, select New session on the pool.
From the CLI:
hansard account pool set coding personal backup --policy ordered --reserve 5hansard account default codinghansard account run --provider codex --binding feature-workhansard account select --pool coding --jsonordereduses the first eligible account in the list.round-robinspreads new sessions across eligible accounts.most-remainingprefers the account with the most quota left in its tightest limit window.- Paused, failed, stale, unverified, and exhausted accounts are skipped. Unknown
quota never counts as available.
--reservedefaults to 0%, and--max-agedefaults to 20 minutes. - A Codex account whose included limits are used up keeps working on its credit
balance. Pools and the router skip it until you turn on Use credits when
limits run out in the Sign-in section of its page, or run
hansard account credits <account> on. It is then used after every account with included usage left. - Launching from a pool checks usage first.
selectpreviews the choice without checking usage or advancing the rotation. defaultsets the pool for a folder and its subfolders; the closest folder wins.--globalsets a fallback.--bindingnames a session so that resuming it uses the same account. If that account becomes unavailable or changes identity, the launch stops instead of switching. Pass the harness’s resume arguments after--. Resuming through a pool requires a binding.forget-bindingreleases a name.- Naming an account directly, as in
hansard account run personal, skips the pool’s quota rules. hansard account routingshows pools, defaults, bindings, and the last 200 launch decisions.
A running session keeps its account until it ends. Hansard never moves a running session to another account or replays its requests.
Start a conversation in the app on one account
Section titled “Start a conversation in the app on one account”When a harness has two or more accounts, the model popover in New conversation has an Account row.
- Select the model chip beside the send button.
- Under Account, choose an account by its name. The first choice leaves the account to the harness.
- Send the first message.
The conversation keeps that account for every later turn. When Routing sends Claude Code or Codex through the router, the first choice is Router chooses, and the row lists the router’s connected accounts. An account lists only the models it serves. If you choose a model that only one account serves, Hansard chooses that account for you. If the account is removed, turned off, signed out, or at its usage limit, the next turn stops with a message that names the account. It never runs on another account. Codex in the app without Routing runs every conversation on one sign-in, so it has no Account row there.
Switch accounts automatically at usage limits
Section titled “Switch accounts automatically at usage limits”Automatic account switching runs a local router that sends each Codex or Claude Code conversation to one of your accounts and moves it to another when a limit is reached.
- Open the Routing tab. Automatic account switching lists each agent installed on this computer, with how many of its accounts are ready and the account it uses next.
- Select Enable beside the tool, or Add account when it has none yet.
- Under How to use your accounts, choose:
- In order starts new conversations on the first available account.
- Spread spreads new conversations across your accounts.
- Rules ranks accounts by rules you order.
- Under Accounts, select the accounts to use. For In order and Spread, set their order by dragging or with the arrow buttons. Under Rules, accounts appear in their order right now, and Edit tie-break order sets the order used for ties and unknown usage. To sign in another account, select Connect account or Connect another account.
- Select Enable. Hansard installs and starts the router and configures the tool.
- Restart the tool, then keep using
codexorclaudeas usual.
The router must stay running while switching is on. After a restart, logout, or crash, the watcher starts it again unless it was last stopped with Stop under Local router. Each tool keeps its own mode and account list. To change them, select Manage. To stop switching and restore the tool’s previous configuration, select Turn off, then restart the tool.
Rules uses the first rule that has an available
account. The rules are Always try first, Accounts with a 5-hour limit,
Nearest weekly reset, Most allowance remaining, Most usage used, and
Your account order.
Drag rules to reorder them, add one from Add a rule, and choose the final
tie breaker in Break ties with. The default uses accounts with a 5-hour
limit first, then the nearest weekly reset, then the most allowance remaining.
A plan with no 5-hour limit, as some Claude and Codex plans have, shows
No 5-hour limit in place of that limit, and a later rule places it. Allowance
compares percentages, not absolute capacity across different plans.
In every mode, a conversation keeps the account it started on until that
account reaches a limit, so its prompt cache stays warm. It then moves once to
the next account. The mode and order apply to new conversations. A temporary
error from the provider stays with the same account, and the tool retries it.
For Claude Code, routing also sets promptCacheTtl to 1h, so a conversation
you come back to within an hour reads its cache instead of processing it again.
Subagents keep the 5-minute cache. If you set up Claude Code routing with an
earlier version, run hansard account proxy client configure claude once to
add the setting, then restart Claude Code.
Codex keeps compacting long conversations on this computer. A compaction made on the provider’s side works only for the account that made it, so a conversation that moved to another account at a limit would fail from then on.
Each row in Accounts shows Next, its place in line, or the reason it is excluded, with its 5-hour and weekly usage and when that usage was checked. It updates as you change the setup.
To write a rule in your own words, select Describe a rule, type your preference, choose an installed Codex or Claude agent in Draft with, and select Draft rule. The agent sees only your typed preference, not your accounts or credentials, and its output is never run as code. If the draft needs a condition the rules cannot express, Hansard lists it and does not apply the draft. Select Use this rule to load it into the preview, then save.
While the router runs, it refreshes rule priorities every minute and reads each routed account’s usage about every two minutes, one request to the provider per account. After a rate limit, that account’s next read waits 5 minutes, doubling up to one hour. Accounts whose usage is older than three minutes, whose check failed, or whose reported reset has passed fall back to their saved order after accounts with known availability. When no account has current usage, the order on the Routing tab reads Using your saved order until usage is checked again. An exhausted account stays skipped until a later check or its reported reset shows it is available. Limits for a single model do not exclude the whole account.
The router keeps an account it rejected with no retry scheduled, such as after the provider refused a login the router cannot renew, unavailable until that account changes. When a usage check through that same account succeeds and shows allowance remaining, Hansard re-enables it for every model. If the provider rejects it again, the next attempt waits 5 minutes, doubling up to one hour, until the account serves a request.
Saved Codex ChatGPT logins stored as files can join without another sign-in:
Codex keeps renewing its own login, and the router receives only the current
access token. Accounts shows the saved login and its router copy as one
connection with one status. Signing in to that login again, from Sign in
or with hansard account login, also renews the router copy and checks it
through the router at once. That sign-in must use the router copy’s workspace.
If the saved login already holds another workspace, the router copy stops
receiving requests and says which account to sign in with. Its Sign in
again opens the saved login’s sign-in in Terminal. Claude needs a separate one-time router sign-in so
that its router and native logins renew independently. Native refresh tokens
are never copied into the router.
Below the tools, the Routing tab lists each routed tool’s accounts in their current order, with 5-hour and weekly usage, the same state the account’s page shows for that login, and when its usage was checked. Check now in the header of Overview refreshes router account usage with every other account’s. The 15-minute usage sample also updates it, including accounts a rule holds out of routing, and applies the rules again, so usage stays current in every mode. A limit whose reset has passed shows as unknown until the next check. Starting the router turns on usage tracking when no Track plan usage setting has been saved.
When a tool is set to use the router but the router is stopped, its row reads Router stopped, because new sessions of that tool cannot connect until the router starts. Router settings on an account of a tool with automatic switching changes whether that tool uses the account; the switching setup sets its priority and weight.
Local router holds the router’s server controls: Restart, Stop, and a menu with the items below. When an update changes the router’s background process, it asks for a restart; the watcher restarts the router after ten minutes without requests.
- Routing settings sets round robin, weighted, or priority-first selection, sticky conversations, and retry limits, which Retry settings shows. Higher priority wins first; weights balance requests within one priority.
- Refresh accounts reloads router account status, and Check for update
installs the router release Hansard has verified. Select Stop first. An
installed router keeps its version until you do this, or until
hansard account proxy stop,hansard account proxy install, andhansard account proxy startreplace it. - Connect another provider signs in router accounts for Antigravity, Devin, Grok, Kimi, Kimi.ai, and Meta, as Sign in through the router does under Add account. If the callback port is busy, paste the callback manually; device-code providers show the code to enter.
Local router lists a tool only when its configuration needs attention, such as a changed default profile, with Restore previous settings when a backup exists. To restore a configured tool, select Manage, then Turn off.
Router accounts also appear in Accounts. Matching native and router memberships share one account page, whose Sign-in section lists each login with its state and controls. Equal emails with different workspaces remain separate. Normal usage capture includes enabled Codex and Claude router accounts in the same history as native logins. Unidentified captures remain under Unassigned captures on Overview, without creating another connected account. Existing logins need no reset or reimport for this grouping.
Sign-in needed means the provider rejected the saved login. In the account’s Sign-in section, select Sign in again for a router login or Sign in for a CLI profile. Reconnecting verifies the same account and workspace and keeps its routing selections and settings. A detected device login offers Sign in on this device. If Sign in again signs in to a different account or workspace than the selected one, the selected account stays as it was and Hansard removes the new router sign-in instead of adding a duplicate.
Codex sign-in ended appears on Accounts when OpenAI ends the Codex sign-in
on this device, so codex cannot start, and the title band counts it as a
connection that needs attention. The notice names the last known account. Run
codex login in a terminal, then select Check again.
Usage unavailable means usage could not be checked; it does not establish that the login expired. Usage check paused means the provider limited usage requests. Connections shows the same issue as the account row, explains its cause, and names the next check time when one is scheduled. Retry usage check checks that router account. Manual and automatic checks respect the provider’s retry delay, and previously captured usage keeps its original time.
Check now checks their quotas with the rest of your usage, up to four at a time; Meta has no quota reader. Manage renames or pauses a router account or edits its priority and weight; under automatic switching, pausing removes it from that tool’s selection. Removing a router account deletes its router sign-in.
The router is an official, checksum-verified CLIProxyAPI release that listens
only on this machine. Its credentials stay in a private folder outside the
archive and sync, and it keeps running when the app restarts or updates. Stop
the router before installing a router update. hansard reset and
hansard uninstall stop the router and restore the tool configuration first;
hansard uninstall --keep-data keeps the router and its credentials.
Hansard installs only the router release it lists as verified, using the
SHA-256 digest included in Hansard. A new upstream release does not install
automatically. Router logs rotate at 2 MB under logs/account-proxy/ in
Hansard home. hansard account proxy status reports the latest startup or
routing refresh failure with its time. Error excerpts remove keys and tokens.
Router states describe the individual connection. Held by routing and
Held for usage limit are rule decisions, not a paused login. Router
error sets a connection aside after a failure while its sign-in still works.
Not in routing means the tool does not select it. Not in use means the
tool does not use the router. Standby keeps a spent account on until its
reset when every account of a model would otherwise be off, so the router keeps
answering for that model; it applies only where Hansard read that nothing can
bill past the account’s limits. Turned off names why, and a router copy
paused by its saved login shows Sign in again with that login. Stale usage
names its check’s age instead of promising a return time. hansard account status prints each account’s states with their reasons in a terminal.
Codex keeps its native ChatGPT sign-in for plugins and connected apps while model
requests use the router’s separate credentials. Router account changes do not
switch plugin accounts. To refresh an older Codex routing configuration, run
hansard account proxy client configure codex and restart Codex.
Routing names the Codex sign-in apart from the model accounts. The Codex sign-in supplies the workspace, plugins, and connected apps; model accounts supply the router’s model capacity. The Codex row shows it only when it needs attention, and Manage shows it with the model accounts. Hansard detects the current Codex sign-in and reports missing or changed sign-in details. Check account reads it again; Change account explains how to sign in through Codex. Reordering model accounts does not change the Codex sign-in. A failed check keeps the last-known identity visible without treating it as a current successful check.
Configured routing applies to new default sessions after restarting Codex. It does not verify which route an already-open conversation is using.
Claude Code works differently. The router signs Claude Code in with a router token, and Claude Code loads your claude.ai connectors, such as Gmail or Google Drive, only when it is signed in with a claude.ai subscription. While switching is on, Claude Code in the terminal, in IDEs, and through the Agent SDK does not load those connectors. Local plugin and MCP configuration remains intact. The Claude desktop app delivers connectors separately. To use synced connectors in Claude Code again, select Turn off and restart Claude Code, or use a separate native profile without router settings.
Other routing integrations have different requirements:
- Grok Build routes advertised
grok-*models through selected Grok accounts. Connect a Grok router account first. Setup retains the native login and restores previous model settings when disabled. Models outside that advertised list keep their configuration. - Antigravity CLI routes Gemini requests through selected Antigravity
accounts. Setup adds a launcher to Bash or Zsh on macOS or Linux. Open a
new terminal before running
agy. Hansard launches receive the routing environment directly. Restoration removes the launcher and preserves unrelated shell edits. Historical Gemini CLI remains import-only. - Muse Code uses selected Meta accounts with In order or Spread.
Meta has no quota reader. Setup saves and restores Muse Code’s settings and
sign-in, retaining unrelated preferences and other provider credentials.
Restart Muse Code after enabling. If setup requests a router restart, run
hansard account proxy restartfirst. - Cursor CLI and Devin CLI use native account pools for new sessions. Their setup rows open native-account setup. They do not join the managed subscription router. Cursor CLI cannot use it to share Codex, Claude, or Grok subscriptions.
The same controls are available from the CLI:
hansard account proxy installhansard account proxy starthansard account proxy statushansard account proxy capturehansard account proxy client configure codexhansard account proxy client configure claudehansard account proxy client restore codexComplete provider sign-in in the app, which handles the sign-in callback.
Change routing for a while
Section titled “Change routing for a while”A temporary override changes how the router handles Codex or Claude Code requests until it ends on its own. Temporary overrides appears on the Routing tab once a tool uses automatic switching.
- Under Temporary overrides, select Add override, or select Temporary override… in an account’s More actions menu.
- Under Override, choose one:
- Use only sends every request to one account.
- Skip leaves one account out, to save its usage.
- Try first sends requests to one account first. The others take over when it is unavailable or at its limit.
- Bypass router points the tool at its own login instead of the router.
- Choose the Account, and the Tool when both tools use the router.
- Under Ends, choose 1 hour, 3 hours, 8 hours, the account’s 5-hour or weekly reset, or When I end it. A bypass offers only the hour choices and When I end it.
- For Use only, under When this account reaches its limit, choose Return to normal routing or Stop sending requests.
- Select Start override.
The title band shows an override while it lasts, and its row under Temporary overrides has End. An override also ends when its account leaves the tool’s routing or routing is turned off; its row then says why until you select Dismiss. A new override for the same account replaces the earlier one, and each tool has one Use only or Try first at a time. Open sessions keep the router during a bypass until they restart, and they need another restart to use the router after the bypass ends.
From the CLI, find an account’s auth index with
hansard account proxy credentials list, then run:
hansard account proxy override set only codex <auth-index> --until five-hour-reset --at-limit fallbackhansard account proxy override set skip claude <auth-index> --until 8hhansard account proxy override set bypass codex --until 3hhansard account proxy override listhansard account proxy override end <override-id>--until takes 1h, 3h, 8h, five-hour-reset, weekly-reset, or off,
which lasts until you end it. A bypass takes only the hour values and off.
Always try an account first
Section titled “Always try an account first”Always try first is a routing rule that keeps one account ahead of a tool’s other accounts. Use it for an account whose usage you never need to save, such as a plan with a 5-hour limit and no weekly limit.
- Open the Routing tab and select Manage beside the tool.
- Under How to use your accounts, select Rules.
- Under Add a rule, select Always try first, then select Add.
- In the new rule, select the account. Only router accounts checked under Accounts appear.
- Select Save.
The rule stays at the top of the Rules list. At its limit, the account leaves the rotation and your other rules choose until it resets. A Try first override still leads while it lasts. To stop, remove the rule with its × button and select Save.
From the CLI, run:
hansard account proxy always-first claude <auth-index> onhansard account proxy always-firsthansard account proxy always-first claude <auth-index> offWithout arguments, always-first lists the account each tool tries first. The
rule needs Rules routing with that account selected.
Continue after a usage limit
Section titled “Continue after a usage limit”If a usage limit interrupts a Codex or Claude Code turn, send Continue in the
same conversation. For a conversation running in Hansard, a Continue button
appears on a recognized limit failure and stays after a page reload. It sends a
new turn with the saved conversation, model, effort, and permission settings.
Completed work stays in place, and the failed prompt is not sent again. Queued
messages wait until the continued turn succeeds.
To continue automatically, turn on Auto-continue after a usage limit in the Routing tab, or run:
hansard config set orchestrate.autoContinueOnLimit trueIt is off by default and needs the router running and configured for that
tool. After two automatic continuations in a row fail, the conversation stops
and shows the Continue button. The setting applies to the next failure
without a restart. It does not affect conversations you run in a terminal;
those still need a manual Continue.
The router switches to another eligible account for the same provider and
model before any output starts. If every account is exhausted, the router
answers a retryable 429 until quota is available again. Claude can report a limit inside a response that has
already started; in that case Continue may try the same account once more,
and the next rejection triggers the switch.
Connect an external router
Section titled “Connect an external router”To use a CLIProxyAPI server you already run, open the Routing tab and, under External routers, select Connect router. Enter a Name, the Local endpoint, and the Management key environment variable, then select Connect. Enter the variable’s name, not the key itself.
From the CLI, set ROUTER_MANAGEMENT_KEY to the server’s management key, then
run:
hansard account router add local --url http://127.0.0.1:8317 --key-env ROUTER_MANAGEMENT_KEYhansard account router status localhansard account router strategy local round-robinHansard saves only the variable name, checks the server’s management interface,
and confirms strategy changes by reading them back. Strategies are
round-robin, weighted-round-robin, and fill-first, and each applies to the
whole router. Manage logins, priorities, weights, and sticky sessions in that
router. Router request counts are not plan quotas, and account pools are not
copied into the router.
How Hansard identifies accounts
Section titled “How Hansard identifies accounts”An account in Hansard has four separate parts: the saved connection, the provider identity, the selected workspace, and the reported plan. Two accounts with different names can share one subscription, and one email address can belong to both a personal and a work membership.
After a native sign-in, Hansard checks the account’s identity. If it matches a membership another saved account already uses, the new account is marked Duplicate workspace and left out of launches and pools:
- Use existing opens the original account.
- Fix sign-in starts sign-in again so you can choose a different workspace.
- Removing the duplicate keeps its provider files.
The original is the earliest registered account. Pausing it does not pass ownership to a duplicate, and a session bound to an account never switches automatically. Matching uses the provider’s membership identifiers, never names, email addresses, or plan labels, so the same email with different verified workspaces is allowed. An identity Hansard cannot resolve is shown as unverified. A failed usage check keeps an earlier duplicate match until a different identity is observed.
Router sign-in can refresh a credential you already have rather than add a new account, and Hansard says when it does. For Codex, Claude, and Devin router accounts, Hansard checks identity after sign-in and pauses a confirmed duplicate, which cannot be re-enabled. Other router providers and browser profiles do not report a verifiable identity. Native accounts and router accounts run their own duplicate checks and never share credentials.
Plan badges use only the plan the provider reports. Hansard never infers a plan from an account name, email, router priority, or API connection label. Within an email group, larger reported plans sort first, and the usage multiplier a plan names or its provider states, such as Claude Ultra’s 10x Pro, breaks ties. This order is a display convention, not a claim that plans have comparable quota.
Supported connection types
Section titled “Supported connection types”| Connection | What Hansard supports |
|---|---|
| Native subscription profiles | Official Codex, Claude Code, Grok Build, Devin, and Cursor CLI sign-in, isolated profiles, usage capture, launches, and pools. For Claude, Hansard selects the Claude subscription login. |
| Muse Code profile | Official device-code sign-in, isolated file credentials, native email and allowance verification, and explicit launches with account run. Muse profiles do not join pools. Meta routing restrictions remain unchanged. |
| Antigravity device account | The device’s official sign-in and operating system keyring, usage capture, and launch. The keyring holds one Google sign-in for each computer user, shared with the Antigravity app, so separate saved sign-ins and native pools are unavailable. Another account takes agy’s /logout and /login, or, while routing is on, Sign in through the router. Routing restrictions remain unchanged. |
| Browser profiles | Separate Chrome or Edge profiles for ChatGPT, Claude.ai, Cursor, Devin, and Grok. Sign-in stays in the browser, cookies stay in the browser’s store, and Hansard cannot verify the membership, read web-chat limits, or route web requests. ChatGPT web limits are separate from Codex plan limits. |
| Usage APIs | Cursor, Factory, GitHub Copilot, and Claude Enterprise reporting credentials. They read usage only and do not sign in to apps or route requests. |
| Managed router | Saved Codex ChatGPT logins, or separate router sign-in for Codex and Claude, plus Antigravity, Devin, Grok, Kimi, Kimi.ai, and Meta. Router support for a provider does not mean that provider allows every third-party use of a subscription. Accounts says under a provider’s heading why the router does not carry it. |
Hansard has no general selector for sign-in methods. API keys, service accounts, federated identities, and cloud credentials are configured in each provider’s own tools. Eligible plans can include claimed API credits, with provider-specific restrictions. A subscription does not grant permission to use every client a provider offers.
Provider sign-in methods and plans
Section titled “Provider sign-in methods and plans”This table summarizes the sign-in methods and plans that each provider shown in Accounts documents. Availability depends on region, workspace policy, and client version, and providers change these often; follow the links for current details. Social login and enterprise SSO happen inside the provider’s own browser flow.
| Provider | Documented sign-in methods | Plans and billing |
|---|---|---|
| OpenAI and Codex | ChatGPT browser sign-in, device authorization, API-key login, enterprise access tokens, and workload identity federation. Browser sign-in supports social accounts, SSO, or email. Custom API providers have separate credentials. Authentication, enterprise tokens, federation. | Free, Go, Plus, Pro 5x and 20x, Business (formerly Team), Edu, and Enterprise, all separate from metered API billing. A generic pro response does not say which multiplier applies. Plans. |
| Claude | Claude subscription sign-in; Console sign-in or API keys; bearer tokens and credential helpers; Anthropic profiles and workload federation; Bedrock, Google Cloud, Foundry, and Claude Platform on AWS. Enterprise browser sign-in can use SSO. Code authentication, browser login. | Free web access, Pro, Max, Ultra, Team Standard and Premium, and Enterprise with usage or seat billing. Organization and member spending caps are separate from short-window limits. Plans, work memberships. |
| Antigravity | Personal browser or keyring sign-in and headless authorization; Gemini API-key mode; enterprise SSO, Cloud project and location, Workforce Identity Federation, and Application Default Credentials. CLI, enterprise. | Individual access, Google AI Plus ($4.99 a month), Pro ($19.99), and Ultra ($99.99 or $199.99), Gemini Enterprise Standard and Plus, and Cloud consumption, each with different entitlements and overage billing. Gemini 4 Argon needs AI Pro, AI Ultra, or an eligible Gemini Enterprise seat; Free and AI Plus do not include it. Plans, Google AI plans. |
| Cursor | Browser sign-in and SAML or OIDC SSO; user API keys, enterprise service accounts, and administration or analytics keys; bring-your-own provider keys, including cloud credentials. The Cursor CLI signs in through the same browser flow, and Hansard saves separate CLI profiles. API, SSO, service accounts, BYOK. | New customers start on The X Subscription: Free, Plus, Premium, Super, Ultra, Teams, and Enterprise, with one weekly pool shared with Grok. Legacy Hobby, regional Start, Pro, Pro+, Ultra, and Teams Standard and Premium plans continue. Model usage pools and bring-your-own-key billing differ. The cloud agent API is not a general chat endpoint. Pricing, legacy plans, usage. |
| Devin | Browser sign-in with manual token fallback, enterprise and legacy Windsurf enterprise sign-in, personal access tokens, and service-user API identities. Legacy API keys and runtime credentials are separate. CLI, enterprise, Windsurf, API. | Free, Pro, Max, Teams full and flex seats, and Enterprise. Daily and weekly limits, shared team credits, enterprise ACUs, and legacy Windsurf credits are not interchangeable. Self-serve billing, enterprise billing. |
| Grok | Browser OIDC, device codes, API keys, external credential commands, and enterprise OIDC; management keys and optional mTLS; Google Vertex and Microsoft Foundry credentials. Web sign-in supports social accounts or email. Build authentication, web login, management API, mTLS, Vertex, Foundry. | The X Subscription (Grok, Cursor, and X): Free, Plus ($8 a month), Premium ($30, 4x), Super ($100, 15x), Ultra ($200, 50x), Teams, and Enterprise, with one weekly pool across Grok products. Earlier SuperGrok and X Premium plans continue. Subscription allowances and extra credits differ from direct API billing. Plans. |
| Factory | Browser or device confirmation, magic links, enterprise SAML or OIDC, personal and service-account keys, and bring-your-own provider keys with headers or credential helpers, including AWS credentials. Identity, CLI, BYOK. | Pro, Plus, Max, Teams, Business, and Enterprise; Plus and Max have different usage multipliers. Factory identity is separate from bring-your-own-key billing. Plans. |
| GitHub Copilot | Browser or device sign-in, supported OAuth tokens, fine-grained personal access tokens with Copilot Requests, and GitHub CLI fallback; SDK server tokens; bring-your-own provider keys. Classic personal access tokens cannot run CLI inference. CLI authentication, server tokens, BYOK. | Free, Student, Pro, Pro+, Max, Business, and Enterprise. A usage-reporting token is separate from a credential that can run models. Plans. |
| Kimi | Official sign-in and Kimi Code membership API keys; separate mainland and overseas endpoints and metered Open Platform keys; compatible-provider credentials. KIMI_CODE_HOME supports separate native profiles, but Hansard manages Kimi through the router. Providers, data locations, membership. |
Go, Plus, Pro, Max, and Ultra; Go has no coding quota. International plans on kimi.ai are Plus ($19 a month), Pro ($39), Max ($99), and Ultra ($199), with a rolling 5-hour Kimi Code limit and no weekly limit. Legacy Andante, Moderato, Allegretto, Allegro, and Vivace memberships keep a weekly limit as well. Devices and keys share one membership allowance. Kimi Code subscriptions are for personal, interactive use. Membership guide, international pricing, community guidelines. |
| Meta | Muse Code browser sign-in or API keys, and a separate bearer key for the Model API. Consumer Meta AI is a different account. Muse Code authentication, Model API authentication. | Muse Code Everyday Usage ($5 a month), High Usage ($15, 5x), Power Usage ($50, 20x), and Maximum Usage ($200, 80x). Muse Wonder Full needs Power Usage or Maximum Usage. Subscription credentials work only in Muse Code; extra API keys use metered Standard or Contributor billing with shared team limits. Plans, subscriptions, API billing. |
| OpenCode | Provider keys, supported provider sign-in, cloud credential chains, Azure Entra, and custom compatible endpoints. Zen and Go use OpenCode-issued keys. Providers. | Zen is metered and Go is a subscription; other providers keep their own billing. Hansard records local activity but does not claim a verified OpenCode-wide quota. Zen, Go. |
Troubleshooting
Section titled “Troubleshooting”The usage chart has a blank stretch. Hansard captured nothing while your Mac slept or the watcher was stopped. That time cannot be filled in later. Turn on Track plan usage to keep sampling.
An account shows Duplicate workspace. It signed in to a workspace another saved account already uses. Select Use existing to open the original, or Fix sign-in to sign in to a different workspace.
Claude Code capture fails. Claude Code versions without the auth command
cannot be checked. Update Claude Code, then select Check now again.
A Codex capture shows the wrong workspace. Codex reports only its active workspace. Switch workspaces in Codex, then capture again.
Rule-based routing does not follow new usage after an upgrade. A router
that was already running keeps its old refresh behavior. Run
hansard account proxy restart.
Account buttons are disabled. A remote or read-only viewer cannot change connections or launch accounts. Open the app on the machine that runs Hansard.