[{"data":1,"prerenderedAt":40},["ShallowReactive",2],{"doc:en:settings-accounts":3},{"title":4,"lede":5,"html":6,"headings":7},"Settings: Claude accounts","The “Claude accounts” tab lists the accounts agents start on, in the order Escouade tries them. Each change is saved right away, without going through “Save”.","\u003Ch2 id=\"how-escouade-picks-an-account\">How Escouade picks an account\u003C\u002Fh2>\n\u003Cp>An account is a Claude Code run with its own configuration folder, so with its own sign-in, sessions, and quota. “Main” is your usual Claude Code: it runs as it always did, with no folder of its own, and it can’t be removed. How accounts and their quotas work is explained in \u003Ca href=\"\u002Fen\u002Fdocs\u002Faccounts\u002F\">accounts\u003C\u002Fa> and in \u003Ca href=\"\u002Fen\u002Fdocs\u002Fusage\u002F\">usage\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>The note under the list’s title sums it up: “New agents start on the first active account under the pause threshold, in this order.” In detail:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A new agent starts on the first active account in the list that has no quota window (5-hour or weekly) at the pause threshold.\u003C\u002Fli>\n\u003Cli>If every active account has reached the threshold, it starts on the first active account, and \u003Ca href=\"\u002Fen\u002Fdocs\u002Fautopilot\u002F\">autopilot\u003C\u002Fa> pauses.\u003C\u002Fli>\n\u003Cli>A project’s “Preferred account”, in the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-projects\u002F\">“Projects”\u003C\u002Fa> tab, goes first as long as it is active.\u003C\u002Fli>\n\u003Cli>An account “Reserved to projects” only receives the agents and tickets of those projects.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"the-list\">The list\u003C\u002Fh2>\n\u003Cp>Each account has its own block in the list.\u003C\u002Fp>\n\u003Cdiv class=\"table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Setting\u003C\u002Fth>\n\u003Cth>Effect\u003C\u002Fth>\n\u003Cth>Default\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Name (the “Name” field)\u003C\u002Ftd>\n\u003Ctd>The account’s name, saved when you leave the field or press \u003Ccode class=\"key\">Enter\u003C\u002Fcode>. An empty name, or one already taken by another account, is refused: the field goes back to the old one.\u003C\u002Ftd>\n\u003Ctd>“Main” for the Main account; the name given at creation for the others\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Active”\u003C\u002Ftd>\n\u003Ctd>Switch. An inactive account receives no new agent. At least one must stay active: the switch of the last active account is grayed out (“At least one account must be active.”).\u003C\u002Ftd>\n\u003Ctd>On\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>↑ and ↓ arrows\u003C\u002Ftd>\n\u003Ctd>Move the account up or down: the order of the list is the order of priority.\u003C\u002Ftd>\n\u003Ctd>—\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Folder”\u003C\u002Ftd>\n\u003Ctd>The account’s configuration folder, shown but not editable.\u003C\u002Ftd>\n\u003Ctd>—\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Executable”\u003C\u002Ftd>\n\u003Ctd>This account’s \u003Ccode class=\"key\">claude\u003C\u002Fcode>. Blank, it is the one in the “Claude Code” tab (the field says “The one in the settings”). Saved when you leave the field.\u003C\u002Ftd>\n\u003Ctd>Blank\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Sign in…” or “Sign in again…”\u003C\u002Ftd>\n\u003Ctd>Opens the account’s sign-in.\u003C\u002Ftd>\n\u003Ctd>—\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Remove”\u003C\u002Ftd>\n\u003Ctd>Takes the account off the list (absent for Main).\u003C\u002Ftd>\n\u003Ctd>—\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Reserved to projects”\u003C\u002Ftd>\n\u003Ctd>One checkbox per open project: the account only serves the projects ticked.\u003C\u002Ftd>\n\u003Ctd>None ticked: “Every project”\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Ch3 id=\"name-and-state\">Name and state\u003C\u002Fh3>\n\u003Cp>Under the name, a colored dot and a text say where the sign-in stands:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>“Checking…” while it is being read;\u003C\u002Fli>\n\u003Cli>“Signed in · ” followed by the claude.ai account’s email, or just “Signed in” when the email isn’t known;\u003C\u002Fli>\n\u003Cli>“Not signed in”;\u003C\u002Fli>\n\u003Cli>“Not signed in with a claude.ai account (API key?)” for Main, which then most likely runs with an API key;\u003C\u002Fli>\n\u003Cli>“Inactive” for a switched-off account.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>When the sign-in exists but is out of date, a line below gives the reason.\u003C\u002Fp>\n\u003Ch3 id=\"folder-and-executable\">Folder and executable\u003C\u002Fh3>\n\u003Cp>For Main, the folder is Claude Code’s own (\u003Ccode class=\"key\">~\u002F.claude\u003C\u002Fcode>, or the one \u003Ccode class=\"key\">CLAUDE_CONFIG_DIR\u003C\u002Fcode> points to). Every other account has its own, which Escouade creates in \u003Ccode class=\"key\">~\u002F.escouade\u002Fclaude\u002F\u003C\u002Fcode>, one subfolder per account. An account can run a different \u003Ccode class=\"key\">claude\u003C\u002Fcode> than the one in the settings, for example a Claude Code in WSL for one and a Windows Claude Code for the other.\u003C\u002Fp>\n\u003Ch3 id=\"signing-in\">Signing in\u003C\u002Fh3>\n\u003Cp>“Sign in…” (“Sign in again…” when the account is already signed in, for example to switch to another claude.ai account) opens a window with a terminal running the account’s \u003Ccode class=\"key\">claude\u003C\u002Fcode>. Sign in there, with the \u003Ccode class=\"key\">\u002Flogin\u003C\u002Fcode> command if Claude Code doesn’t offer it. Escouade checks for the sign-in every 2 seconds: as soon as it is done, the window shows “Signed in as” followed by the email, closes the terminal, and reads the account’s quota. If you close the window before that, the account stays, not signed in. If Claude Code stops before the sign-in, the window says so and offers “Restart”.\u003C\u002Fp>\n\u003Ch3 id=\"reserved-to-projects\">Reserved to projects\u003C\u002Fh3>\n\u003Cp>The checkboxes keep an account to those projects alone (a client’s projects, say): other projects never start on it. With nothing ticked, the account serves every project, which the row says as “Every project”. Main can be reserved like any other.\u003C\u002Fp>\n\u003Cp>If no active account serves a project (all are reserved to others, or switched off), a line under the list names the project and says its agents and tickets won’t start.\u003C\u002Fp>\n\u003Ch3 id=\"removing-an-account\">Removing an account\u003C\u002Fh3>\n\u003Cp>“Remove” asks for confirmation. The dialog reminds you that new agents will no longer start on the account, and that its folder stays on the disk, with its sign-in and its conversations. While agents that are not archived still run on the account, removal is refused. Projects that preferred it go back to “Automatic”.\u003C\u002Fp>\n\u003Ch2 id=\"adding-an-account\">Adding an account\u003C\u002Fh2>\n\u003Cp>“Add an account…”, under the list, opens the “Add a Claude account” window.\u003C\u002Fp>\n\u003Col>\n\u003Cli>“Name”: the new account’s name (“Pro, Team…” as an example). Two accounts can’t have the same name.\u003C\u002Fli>\n\u003Cli>“Share with Main”: checkboxes, all ticked at first, for the items of Main’s folder the account takes over. The files are \u003Ccode class=\"key\">settings.json\u003C\u002Fcode> and \u003Ccode class=\"key\">CLAUDE.md\u003C\u002Fcode>, the folders \u003Ccode class=\"key\">skills\u003C\u002Fcode>, \u003Ccode class=\"key\">agents\u003C\u002Fcode>, \u003Ccode class=\"key\">commands\u003C\u002Fcode>, \u003Ccode class=\"key\">plugins\u003C\u002Fcode>, \u003Ccode class=\"key\">hooks\u003C\u002Fcode>, and \u003Ccode class=\"key\">output-styles\u003C\u002Fcode>; only the ones Main has are offered.\u003C\u002Fli>\n\u003Cli>“Sharing”: “Link (a change applies to both accounts)”, the default, or “Copy”. On Windows, folders are linked with a junction, which needs no administrator rights, and files are copied, since a file link would need them. On macOS and Linux, folders and files are linked with symbolic links; the “copied (linking a file needs administrator rights)” note the window shows next to the files only holds for Windows, even though it also appears on Linux.\u003C\u002Fli>\n\u003Cli>“Create and sign in” creates the account, active and last in the list, with its folder in \u003Ccode class=\"key\">~\u002F.escouade\u002Fclaude\u002F\u003C\u002Fcode>, then opens its sign-in.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The sign-in (\u003Ccode class=\"key\">.credentials.json\u003C\u002Fcode>) and \u003Ccode class=\"key\">.claude.json\u003C\u002Fcode> are never shared: each account has its own.\u003C\u002Fp>\n\u003Ch2 id=\"the-pause-threshold\">The pause threshold\u003C\u002Fh2>\n\u003Cp>The threshold is set in the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-board\u002F\">“Kanban”\u003C\u002Fa> tab, not here, but it decides which accounts Escouade sets aside.\u003C\u002Fp>\n\u003Cdiv class=\"table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Setting\u003C\u002Fth>\n\u003Cth>Effect\u003C\u002Fth>\n\u003Cth>Default\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>“Pause above quota” (for all projects)\u003C\u002Ftd>\n\u003Ctd>No ticket starts while the 5-hour window or the weekly window is at or above this threshold. Choices: 80%, 90%, 95%, or 100%.\u003C\u002Ftd>\n\u003Ctd>100%\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>An account with a window past the threshold is set aside in favor of the next one in the list, and the quota panel marks it “past the pause threshold”.\u003C\u002Fp>\n\u003Ch2 id=\"resuming-on-another-account\">Resuming on another account\u003C\u002Fh2>\n\u003Cp>When a turn stops on the usage limit, the agent’s card offers “Resume on” followed by an account, or “Resume on another account” with a menu when there are several: the agent goes on with its session on the other account. The accounts offered are the active ones, other than the agent’s own, that serve its project, are signed in, and stay under the pause threshold.\u003C\u002Fp>\n\u003Cp>For a ticket’s agent, the “Resume a ticket’s agent stopped by the usage limit on another account” setting in the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-claude-code\u002F\">“Claude Code”\u003C\u002Fa> tab does it by itself. A session doesn’t move from an account that runs Claude Code on Windows to one that runs it in WSL, or the other way around.\u003C\u002Fp>\n",[8,12,15,19,22,25,28,31,34,37],{"id":9,"text":10,"depth":11},"how-escouade-picks-an-account","How Escouade picks an account",2,{"id":13,"text":14,"depth":11},"the-list","The list",{"id":16,"text":17,"depth":18},"name-and-state","Name and state",3,{"id":20,"text":21,"depth":18},"folder-and-executable","Folder and executable",{"id":23,"text":24,"depth":18},"signing-in","Signing in",{"id":26,"text":27,"depth":18},"reserved-to-projects","Reserved to projects",{"id":29,"text":30,"depth":18},"removing-an-account","Removing an account",{"id":32,"text":33,"depth":11},"adding-an-account","Adding an account",{"id":35,"text":36,"depth":11},"the-pause-threshold","The pause threshold",{"id":38,"text":39,"depth":11},"resuming-on-another-account","Resuming on another account",1791926756555]