Model accounts
A model account is the AI account a runner signs in as to do a task's work: a subscription a person signs in to on a node, or an API key Jaah stores. Every task run uses one, so your organization needs at least one that works before any task can run.
You find them in the sidebar under Directory, then AI Accounts. Each run picks an enabled account that fits its task and has room, subscriptions first; you never pick one by hand. A subscription runs only on nodes where it is signed in and reports its quota; an API key runs on any node and is billed per token by the provider. Adding and signing in accounts needs permission to add them; changing, disabling or removing one needs the Org Owner or Org Admin role.
Start with the first guide when your organization has no working account. The rest keep accounts healthy and shared the way you want:
- Add a model account — add an API key or sign a subscription in on a node.
- Sign a model account in again — renew a subscription whose sign-in expired or was refused.
- Add a subscription to another node — sign a subscription in on one more node, or take it off one.
- Pause or remove a model account — stop runs using an account for a while, or remove it for good.
- Move a model account between consoles — export an account and import it into another console.
- Limit how a model account is used — keep an account for tasks that pick its provider, and cap its runners.
- Share a model account with people — give people or groups a role on one account, and take it away again.
- Replace a model account's API key — put a rotated or new key on an account without adding another.
- Change a model account's owner — share a member's account with the organization, or hand it to another member.
- Check how much of a model account's quota is left — read each window's use and reset, and keep tasks running when an account runs out.
- Find out why a model account isn't running tasks — read an idle account's mark, chips and node states, and put it back in rotation.
- Check whether your model accounts are ready — as a member, read each account's mark and know what to do when one isn't ready.
- Run your tasks on your own subscription — sign your own subscription in as a personal account your tasks can run on.
- Rename a model account or describe it — give an account a clearer name, or a description that says what it is for.
- Set how many runners each subscription runs — change Concurrent runners, the cap on runners per subscription account.
- Choose the node a subscription signs in on: pick where a subscription signs in, see which nodes hold it, and what to do when no node can take it.
- Add a model account for another agent — add an account for an agent other than Claude Code, read its limitations, and keep it for tasks that ask for it.
- Set the workspace an API key account's requests use — fill in Workspace ID for a key not scoped to one Anthropic workspace, or clear it.
Every column, chip and setting is described in the Model accounts reference. For how runs pick an account, quotas and how a model account differs from a credential, see How model accounts work.