[{"data":1,"prerenderedAt":55},["ShallowReactive",2],{"doc:en:settings-claude-code":3},{"title":4,"lede":5,"html":6,"headings":7},"Settings: Claude Code","The “Claude Code” tab sets the Claude Code executable, the model, effort, and permission mode of new agents, how Claude processes live, and the server that lets Claude drive Escouade.","\u003Ch2 id=\"executable\">Executable\u003C\u002Fh2>\n\u003Cp>The “Executable” group has a single field.\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>“Executable path” (blank = detect automatically)\u003C\u002Ftd>\n\u003Ctd>The \u003Ccode class=\"key\">claude\u003C\u002Fcode> Escouade runs for agents. An account with its own executable, in the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-accounts\u002F\">“Claude accounts”\u003C\u002Fa> tab, runs its own.\u003C\u002Ftd>\n\u003Ctd>Blank\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Ch3 id=\"where-escouade-looks\">Where Escouade looks\u003C\u002Fh3>\n\u003Cp>With the field blank, Escouade looks for \u003Ccode class=\"key\">claude\u003C\u002Fcode> in the \u003Ccode class=\"key\">PATH\u003C\u002Fcode>, then in the installers’ usual locations:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>on Windows: \u003Ccode>~\\.local\\bin\\claude.exe\u003C\u002Fcode>, \u003Ccode>~\\.claude\\local\\claude.exe\u003C\u002Fcode>, and \u003Ccode>~\\AppData\\Roaming\\npm\\claude.cmd\u003C\u002Fcode>;\u003C\u002Fli>\n\u003Cli>on macOS and Linux: \u003Ccode class=\"key\">~\u002F.local\u002Fbin\u002Fclaude\u003C\u002Fcode>, \u003Ccode>~\u002F.claude\u002Flocal\u002Fclaude\u003C\u002Fcode>, \u003Ccode>\u002Fopt\u002Fhomebrew\u002Fbin\u002Fclaude\u003C\u002Fcode>, and \u003Ccode>\u002Fusr\u002Flocal\u002Fbin\u002Fclaude\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>On Windows, if it finds none, Escouade looks for a Claude Code installed in WSL, in the distribution named by “WSL distribution” in the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-terminals\u002F\">“Terminals”\u003C\u002Fa> tab (blank = the default distribution).\u003C\u002Fp>\n\u003Cp>With the field filled in, you can write:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>a full path;\u003C\u002Fli>\n\u003Cli>a path starting with \u003Ccode class=\"key\">~\u003C\u002Fcode>, the home folder (Windows, macOS, and Linux);\u003C\u002Fli>\n\u003Cli>on Windows, a path without its \u003Ccode class=\"key\">.exe\u003C\u002Fcode> or \u003Ccode class=\"key\">.cmd\u003C\u002Fcode>;\u003C\u002Fli>\n\u003Cli>on Windows, a Claude Code installed in WSL: \u003Ccode class=\"key\">~\u002F.local\u002Fbin\u002Fclaude\u003C\u002Fcode>, \u003Ccode>\u002Fhome\u002F<user>\u002F.local\u002Fbin\u002Fclaude\u003C\u002Fcode>, or \u003Ccode>\\\\wsl.localhost\\<distribution>\\home\\<user>\\.local\\bin\\claude\u003C\u002Fcode> (\u003Ccode>\\\\wsl$\\<distribution>\\…\u003C\u002Fcode> works too).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3 id=\"the-line-under-the-field\">The line under the field\u003C\u002Fh3>\n\u003Cp>A quarter of a second after you stop typing, Escouade looks for the \u003Ccode class=\"key\">claude\u003C\u002Fcode> in the field and says what it found under the field:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>“Found: ” followed by the path;\u003C\u002Fli>\n\u003Cli>“Found in WSL (Ubuntu): ” followed by the Linux path, for a Claude Code in WSL;\u003C\u002Fli>\n\u003Cli>“Not found.”: on Windows the line then recalls the accepted path forms, WSL’s included; elsewhere it says “Not found. Give the path to claude.”.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>With the field blank, the placeholder already says whether \u003Ccode class=\"key\">claude\u003C\u002Fcode> is found: “claude (found in PATH)” or “not found — enter the path to claude.exe”. After “Save”, a new path or a new WSL distribution triggers another search, to update the banner on the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fboard\u002F\">Kanban\u003C\u002Fa> and the text of the field.\u003C\u002Fp>\n\u003Cdiv class=\"callout warning\">\u003Cp class=\"callout-title\">Warning\u003C\u002Fp>\u003Cp>If the \u003Ccode class=\"key\">claude\u003C\u002Fcode> found is in WSL and WSL’s network is NAT, a warning is added: Escouade’s MCP server and the tracking of the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fclaude-code-view\u002F\">Claude Code view\u003C\u002Fa> can’t reach the app. Switch WSL to mirrored mode (\u003Ccode>networkingMode=mirrored\u003C\u002Fcode> under \u003Ccode class=\"key\">[wsl2]\u003C\u002Fcode> in \u003Ccode>%UserProfile%\\.wslconfig\u003C\u002Fcode>), then run \u003Ccode>wsl --shutdown\u003C\u002Fcode>.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"new-agents\">New agents\u003C\u002Fh2>\n\u003Cp>The three choices apply to every \u003Ca href=\"\u002Fen\u002Fdocs\u002Fmanaging-agents\u002F\">agent\u003C\u002Fa> created afterward. In an agent’s message field you can change them for that agent alone. Kanban tickets take them too when the project’s \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-board\u002F\">“Kanban”\u003C\u002Fa> tab doesn’t pick its own.\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>“Default model”\u003C\u002Ftd>\n\u003Ctd>One of Claude Code’s aliases: “Fable”, “Opus”, “Sonnet”, or “Haiku”. Once Claude Code has said which version it runs for an alias, the chip shows it (“Sonnet 5.5”, for example).\u003C\u002Ftd>\n\u003Ctd>“Sonnet”\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Default effort”\u003C\u002Ftd>\n\u003Ctd>How much the model thinks before answering.\u003C\u002Ftd>\n\u003Ctd>“Medium”\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Default permission mode”\u003C\u002Ftd>\n\u003Ctd>What Claude may do without asking you.\u003C\u002Ftd>\n\u003Ctd>“Auto”\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Ch3 id=\"effort-levels\">Effort levels\u003C\u002Fh3>\n\u003Cdiv class=\"table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Level\u003C\u002Fth>\n\u003Cth>Meaning\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>“Low”\u003C\u002Ftd>\n\u003Ctd>Quick answers, little thinking\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Medium”\u003C\u002Ftd>\n\u003Ctd>Balanced\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“High”\u003C\u002Ftd>\n\u003Ctd>Deep thinking\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Very high”\u003C\u002Ftd>\n\u003Ctd>Very deep thinking\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Max”\u003C\u002Ftd>\n\u003Ctd>Maximum thinking, uses more tokens\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Ch3 id=\"permission-modes\">Permission modes\u003C\u002Fh3>\n\u003Cdiv class=\"table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Mode\u003C\u002Fth>\n\u003Cth>Meaning\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>“Auto”\u003C\u002Ftd>\n\u003Ctd>A classifier approves safe actions and asks about the rest\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Ask”\u003C\u002Ftd>\n\u003Ctd>Claude asks for your approval before each sensitive action\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Plan”\u003C\u002Ftd>\n\u003Ctd>Claude analyzes and proposes a plan without changing anything\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Accept edits”\u003C\u002Ftd>\n\u003Ctd>File edits are accepted without asking\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Bypass”\u003C\u002Ftd>\n\u003Ctd>No permission requests (only for safe environments)\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>Permission requests and how to answer them are described in \u003Ca href=\"\u002Fen\u002Fdocs\u002Fchat\u002F\">the conversation\u003C\u002Fa>, and “Plan” mode in \u003Ca href=\"\u002Fen\u002Fdocs\u002Fplan\u002F\">the plan\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"callout note\">\u003Cp class=\"callout-title\">Note\u003C\u002Fp>\u003Cp>With Haiku, the effort choice is grayed out in the agent’s message field (“Haiku doesn’t support effort”), and so is “Auto” mode (“unavailable with Haiku”).\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"processes\">Processes\u003C\u002Fh2>\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>“Auto-resume after the usage limit”\u003C\u002Ftd>\n\u003Ctd>“continue” is sent to the agent once the quota has reset.\u003C\u002Ftd>\n\u003Ctd>On\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Resume a ticket’s agent stopped by the usage limit on another account”\u003C\u002Ftd>\n\u003Ctd>Otherwise it waits for its account to reset. Absent while there is only one account.\u003C\u002Ftd>\n\u003Ctd>Off\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Open new agents in Claude Code’s interface”\u003C\u002Ftd>\n\u003Ctd>A new agent runs in the Claude Code view rather than in Escouade’s conversation.\u003C\u002Ftd>\n\u003Ctd>Off\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Agents keep a task list”\u003C\u002Ftd>\n\u003Ctd>Agents get Claude Code’s task list tool.\u003C\u002Ftd>\n\u003Ctd>On\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Stop idle Claude processes after” (minutes, 0 = never)\u003C\u002Ftd>\n\u003Ctd>The Claude process of an idle agent is stopped after this delay.\u003C\u002Ftd>\n\u003Ctd>30\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Ch3 id=\"auto-resume\">Auto-resume\u003C\u002Fh3>\n\u003Cp>When an agent stops on the usage limit, Escouade plans to write “continue” to it when the quota resets. Turning the setting off also cancels the resumes already planned. The limit and the quotas are explained in \u003Ca href=\"\u002Fen\u002Fdocs\u002Fusage\u002F\">usage\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3 id=\"resume-on-another-account\">Resume on another account\u003C\u002Fh3>\n\u003Cp>With several accounts, a ticket’s agent stopped by the limit goes on by itself, with its session, on the account Escouade would pick, when another one is usable, instead of waiting for its own account to reset. See \u003Ca href=\"\u002Fen\u002Fdocs\u002Faccounts\u002F\">accounts\u003C\u002Fa> and the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-accounts\u002F\">“Claude accounts”\u003C\u002Fa> tab.\u003C\u002Fp>\n\u003Ch3 id=\"claude-code-view\">Claude Code view\u003C\u002Fh3>\n\u003Cp>Each agent switches views from its header, and this setting only picks the starting view. Ticket agents stay in Escouade’s view. See \u003Ca href=\"\u002Fen\u002Fdocs\u002Fclaude-code-view\u002F\">the Claude Code view\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3 id=\"task-list\">Task list\u003C\u002Fh3>\n\u003Cp>If the agent keeps a list, Escouade shows its progress in the “Plan” banner; the model doesn’t have to use it. The setting applies to agents started afterward. See \u003Ca href=\"\u002Fen\u002Fdocs\u002Fplan\u002F\">the plan\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3 id=\"idle-processes\">Idle processes\u003C\u002Fh3>\n\u003Cp>The field is a number of minutes; 0 means never, and an empty field counts as 0. The session of an agent whose process was stopped stays resumable. An agent in remote control is never stopped this way, so that it stays reachable from claude.ai.\u003C\u002Fp>\n\u003Ch2 id=\"escouade-in-claude\">Escouade in Claude\u003C\u002Fh2>\n\u003Cp>This group lets Claude Code, in a terminal, in another tool, or in an Escouade agent, read your projects, agents, and tickets, and create tickets or start agents, through Escouade’s \u003Ca href=\"\u002Fen\u002Fdocs\u002Fmcp\u002F\">MCP server\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3 id=\"claude-can-drive-escouade\">Claude can drive Escouade\u003C\u002Fh3>\n\u003Cp>The switch is off by default. It saves right away, without going through “Save”: turning it on declares the server in the Claude Code config of each active account, which a “Cancel” could not undo. Turning it off changes the token and removes the server from each account.\u003C\u002Fp>\n\u003Cp>As long as a project lets its agents use Escouade (the “Agents can use Escouade” setting in the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-projects\u002F\">“Projects”\u003C\u002Fa> tab), the server runs even with the switch off.\u003C\u002Fp>\n\u003Cp>With the switch on, a line below it says where the declaration stands:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>“Declaring in Claude…” while Escouade writes the server into Claude Code’s config;\u003C\u002Fli>\n\u003Cli>“Declared in Claude · Main account, Pro account” when it is done for the accounts listed;\u003C\u002Fli>\n\u003Cli>“Not declared for the Pro account: ” followed by the reason, when it failed for an account: the window then shows the command to run by hand (introduced by “Run it by hand in PowerShell:”, or “… in sh:” on macOS), with the token masked, and the “Copy the command” button copies the real command (“Command copied”);\u003C\u002Fli>\n\u003Cli>“The server did not start: ” followed by the reason, in place of the lines above.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"callout warning\">\u003Cp class=\"callout-title\">Warning\u003C\u002Fp>\u003Cp>The token is written in plain text in Claude Code’s config (\u003Ccode class=\"key\">~\u002F.claude.json\u003C\u002Fcode> for the Main account). Turning it off changes the token.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"mcp-activity\">MCP activity\u003C\u002Fh2>\n\u003Cp>This last group, “MCP activity”, lists what the server received and answered, the most recent calls first. Each line gives the time, who called (an agent’s name, “Claude (outside Escouade)”, or, for a request refused before it is known who sent it, “Unknown client”), the tool, the result (“Done”, “Refused”, or “Error”), then what was asked and, for a refusal or an error, why. The last 200 calls are kept in memory, not saved. The “Clear” button empties the list; with no calls, it says “No calls yet.”.\u003C\u002Fp>\n",[8,12,16,19,22,25,28,31,34,37,40,43,46,49,52],{"id":9,"text":10,"depth":11},"executable","Executable",2,{"id":13,"text":14,"depth":15},"where-escouade-looks","Where Escouade looks",3,{"id":17,"text":18,"depth":15},"the-line-under-the-field","The line under the field",{"id":20,"text":21,"depth":11},"new-agents","New agents",{"id":23,"text":24,"depth":15},"effort-levels","Effort levels",{"id":26,"text":27,"depth":15},"permission-modes","Permission modes",{"id":29,"text":30,"depth":11},"processes","Processes",{"id":32,"text":33,"depth":15},"auto-resume","Auto-resume",{"id":35,"text":36,"depth":15},"resume-on-another-account","Resume on another account",{"id":38,"text":39,"depth":15},"claude-code-view","Claude Code view",{"id":41,"text":42,"depth":15},"task-list","Task list",{"id":44,"text":45,"depth":15},"idle-processes","Idle processes",{"id":47,"text":48,"depth":11},"escouade-in-claude","Escouade in Claude",{"id":50,"text":51,"depth":15},"claude-can-drive-escouade","Claude can drive Escouade",{"id":53,"text":54,"depth":11},"mcp-activity","MCP activity",1791926756538]