[{"data":1,"prerenderedAt":40},["ShallowReactive",2],{"doc:en:installation":3},{"title":4,"lede":5,"html":6,"headings":7},"Installation","The requirements of each system, installing on Windows, macOS and Linux, using a Claude Code installed in WSL, the PATH on macOS, then what you see at first launch and where updates come from.","\u003Ch2 id=\"requirements\">Requirements\u003C\u002Fh2>\n\u003Cdiv class=\"table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Item\u003C\u002Fth>\n\u003Cth>Windows\u003C\u002Fth>\n\u003Cth>macOS\u003C\u002Fth>\n\u003Cth>Linux\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>System\u003C\u002Ftd>\n\u003Ctd>Windows 10 or 11 (WebView2, present by default on Windows 11)\u003C\u002Ftd>\n\u003Ctd>macOS 11 (Big Sur) or later, on Apple Silicon or Intel Macs\u003C\u002Ftd>\n\u003Ctd>x86-64, glibc 2.35 or later (Ubuntu 22.04, Debian 12, Fedora 36 and later), with WebKitGTK 4.1\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Git\u003C\u002Ftd>\n\u003Ctd>Git for Windows\u003C\u002Ftd>\n\u003Ctd>The Xcode command-line tools (\u003Ccode>xcode-select --install\u003C\u002Fcode>) or Homebrew’s\u003C\u002Ftd>\n\u003Ctd>Your distribution’s\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>On top of that:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Claude Code\u003C\u002Fstrong>, installed and signed in to your Claude account, the way you would for using it in a terminal (see the \u003Ca href=\"https:\u002F\u002Fcode.claude.com\u002Fdocs\u002Fen\u002Foverview\" rel=\"noopener\">Claude Code documentation\u003C\u002Fa>). Escouade starts the \u003Ccode class=\"key\">claude\u003C\u002Fcode> of your machine.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Git\u003C\u002Fstrong>: Escouade uses it for diffs, commits, branches and worktrees. If a project’s folder is not a repository, Escouade initializes one when you create the project.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Optional on Windows\u003C\u002Fstrong>: PowerShell 7 (without it, the built-in terminals use Windows PowerShell) and WSL.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3 id=\"where-escouade-looks-for-claude-code\">Where Escouade looks for Claude Code\u003C\u002Fh3>\n\u003Cp>Escouade looks for \u003Ccode class=\"key\">claude\u003C\u002Fcode> in this order:\u003C\u002Fp>\n\u003Col>\n\u003Cli>the path in Settings › Claude Code › “Executable path”, if it is not blank (it is then the only place tried);\u003C\u002Fli>\n\u003Cli>the \u003Ccode class=\"key\">PATH\u003C\u002Fcode>;\u003C\u002Fli>\n\u003Cli>the places where the Claude Code installers put it (table below);\u003C\u002Fli>\n\u003Cli>on Windows, when there is none, a Claude Code installed in WSL (see \u003Ca href=\"#claude-code-in-wsl\">below\u003C\u002Fa>).\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cdiv class=\"table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>System\u003C\u002Fth>\n\u003Cth>Places tried\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Windows\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>%UserProfile%\\.local\\bin\\claude.exe\u003C\u002Fcode>, \u003Ccode>%UserProfile%\\.claude\\local\\claude.exe\u003C\u002Fcode>, \u003Ccode>%UserProfile%\\AppData\\Roaming\\npm\\claude.cmd\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>macOS and Linux\u003C\u002Ftd>\n\u003Ctd>\u003Ccode class=\"key\">~\u002F.local\u002Fbin\u002Fclaude\u003C\u002Fcode>, \u003Ccode>~\u002F.claude\u002Flocal\u002Fclaude\u003C\u002Fcode>, \u003Ccode>\u002Fopt\u002Fhomebrew\u002Fbin\u002Fclaude\u003C\u002Fcode>, \u003Ccode>\u002Fusr\u002Flocal\u002Fbin\u002Fclaude\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>The path in the settings accepts \u003Ccode class=\"key\">~\u003C\u002Fcode> for your home folder, and on Windows it can leave out \u003Ccode class=\"key\">.exe\u003C\u002Fcode> or \u003Ccode class=\"key\">.cmd\u003C\u002Fcode>. Leave the field blank to detect it automatically. The line under the field says where Escouade found \u003Ccode class=\"key\">claude\u003C\u002Fcode> (“Found: …”) or, when it is not found, the path forms it accepts.\u003C\u002Fp>\n\u003Cp>Without Claude Code, the welcome screen says so, so does an agent’s empty conversation, and the Kanban starts no tickets (“Claude Code not found — no tickets will start”). Install it or set its path in the settings: when you save another path, these messages update without restarting Escouade.\u003C\u002Fp>\n\u003Ch2 id=\"installing-escouade\">Installing Escouade\u003C\u002Fh2>\n\u003Cp>The installers are on the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fguillaume-gagnaire\u002Fescouade\u002Freleases\u002Flatest\" rel=\"noopener\">GitHub releases\u003C\u002Fa> page.\u003C\u002Fp>\n\u003Ch3 id=\"windows\">Windows\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Download the \u003Ccode class=\"key\">.exe\u003C\u002Fcode> installer of the latest release.\u003C\u002Fli>\n\u003Cli>Run it. It installs Escouade for your user account, without asking for administrator rights, and it speaks the system language (French or English).\u003C\u002Fli>\n\u003Cli>Open Escouade from the Start menu.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cdiv class=\"callout note\">\u003Cp class=\"callout-title\">Note\u003C\u002Fp>\u003Cp>Escouade used to be called “Claude Code Manager”. Installed over an old version, it replaces it and keeps your settings and conversations.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Ch3 id=\"macos\">macOS\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Download the \u003Ccode class=\"key\">.dmg\u003C\u002Fcode> of the latest release. It is universal: the same file works on Apple Silicon and Intel Macs.\u003C\u002Fli>\n\u003Cli>Open it and drag Escouade into the Applications folder.\u003C\u002Fli>\n\u003Cli>Launch Escouade.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The app is signed with an Apple Developer ID certificate and notarized by Apple: macOS opens it without asking for any authorization.\u003C\u002Fp>\n\u003Ch3 id=\"linux\">Linux\u003C\u002Fh3>\n\u003Cp>The \u003Ccode class=\"key\">AppImage\u003C\u002Fcode> runs on any distribution that meets the requirements:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-sh\">chmod +x Escouade_*.AppImage\n.\u002FEscouade_*.AppImage\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>It is the one the built-in update replaces. On Debian or Ubuntu you can also install the \u003Ccode class=\"key\">.deb\u003C\u002Fcode> package:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-sh\">sudo apt install .\u002FEscouade_*_amd64.deb\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>On Linux, the tokens of the integrations (Jira, Trello, GitHub, Linear) are kept in \u003Ccode>~\u002F.escouade\u002Fintegrations.json\u003C\u002Fcode>, because no system keychain is supported.\u003C\u002Fp>\n\u003Ch2 id=\"claude-code-in-wsl\">Claude Code in WSL\u003C\u002Fh2>\n\u003Cp>On Windows, Escouade can run a Claude Code installed in WSL.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Install Claude Code in your WSL distribution and sign it in.\u003C\u002Fli>\n\u003Cli>Open Settings › Claude Code. In “Executable path”, enter the path of \u003Ccode class=\"key\">claude\u003C\u002Fcode> in one of these forms:\u003Cul>\n\u003Cli>\u003Ccode class=\"key\">~\u002F.local\u002Fbin\u002Fclaude\u003C\u002Fcode>;\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fhome\u002F<user>\u002F.local\u002Fbin\u002Fclaude\u003C\u002Fcode>;\u003C\u002Fli>\n\u003Cli>\u003Ccode>\\\\wsl.localhost\\<distribution>\\home\\<user>\\.local\\bin\\claude\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Leave the field blank if Windows has no \u003Ccode class=\"key\">claude\u003C\u002Fcode>: Escouade then looks for its own in WSL, in the usual places (\u003Ccode class=\"key\">~\u002F.local\u002Fbin\u002Fclaude\u003C\u002Fcode> first).\u003C\u002Fli>\n\u003Cli>Read the line under the field: “Found in WSL (Ubuntu): …” confirms that \u003Ccode class=\"key\">claude\u003C\u002Fcode> is found, and in which distribution.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The distribution used is the one the path names (\u003Ccode>\\\\wsl.localhost\\<distribution>\\…\u003C\u002Fcode>), otherwise the one in Settings › Terminals › “WSL distribution”, otherwise WSL’s default distribution.\u003C\u002Fp>\n\u003Cp>Escouade starts \u003Ccode class=\"key\">claude\u003C\u002Fcode> through \u003Ccode class=\"key\">wsl.exe\u003C\u002Fcode>, in the agent’s folder (seen from WSL under \u003Ccode class=\"key\">\u002Fmnt\u002Fc\u002F…\u003C\u002Fcode>). Its sessions, sign-in and quota are read from the Linux home folder. A project folder that WSL can’t reach (a network share, another distribution’s folder) is refused.\u003C\u002Fp>\n\u003Cdiv class=\"callout warning\">\u003Cp class=\"callout-title\">Warning\u003C\u002Fp>\u003Cp>Escouade’s MCP tools and the live tracking of the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fclaude-code-view\u002F\">Claude Code view\u003C\u002Fa> need WSL’s mirrored networking. Add \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>. When WSL’s network is in NAT mode, the settings say so under the path field.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Cp>Claude Code is started in WSL without the shell profile: a variable set in \u003Ccode class=\"key\">~\u002F.profile\u003C\u002Fcode> or \u003Ccode class=\"key\">~\u002F.bashrc\u003C\u002Fcode> does not reach it.\u003C\u002Fp>\n\u003Ch2 id=\"the-path-on-macos\">The PATH on macOS\u003C\u002Fh2>\n\u003Cp>An app started from the Finder or the Dock does not receive your terminal’s \u003Ccode class=\"key\">PATH\u003C\u002Fcode>: without a precaution, a \u003Ccode class=\"key\">claude\u003C\u002Fcode> or a \u003Ccode class=\"key\">git\u003C\u002Fcode> installed with Homebrew would not be found. So at startup Escouade asks your login shell for its \u003Ccode class=\"key\">PATH\u003C\u002Fcode> (\u003Ccode>$SHELL -ilc\u003C\u002Fcode>, with 5 seconds to answer) and merges it with the one it received: the shell’s folders first, then those already there, without duplicates. It adds \u003Ccode class=\"key\">\u002Fopt\u002Fhomebrew\u002Fbin\u003C\u002Fcode>, \u003Ccode class=\"key\">\u002Fusr\u002Flocal\u002Fbin\u003C\u002Fcode> and \u003Ccode class=\"key\">~\u002F.local\u002Fbin\u003C\u002Fcode> if they are not there. This \u003Ccode class=\"key\">PATH\u003C\u002Fcode> is the one of every process it starts: Claude Code, git and the commands of the agents.\u003C\u002Fp>\n\u003Cp>On Linux the same mechanism applies, which matters when Escouade is started from the desktop launcher rather than from a terminal.\u003C\u002Fp>\n\u003Cp>If \u003Ccode class=\"key\">claude\u003C\u002Fcode> is still not found, set its path in Settings › Claude Code.\u003C\u002Fp>\n\u003Ch2 id=\"first-launch\">First launch\u003C\u002Fh2>\n\u003Cp>As long as no project exists, Escouade opens a welcome screen: its logo, the sentence “Add a project to run Claude Code agents, follow their questions, and open terminals.” and the “+ Add a project” button.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>If Claude Code is not found, a warning says so: “Claude Code couldn’t be found on this machine. Install it (\u003Ccode>irm https:\u002F\u002Fclaude.ai\u002Finstall.ps1 | iex\u003C\u002Fcode>) or set its path in the settings.” Then open the settings with the ⚙ button of the status bar or \u003Ccode class=\"key\">Ctrl+,\u003C\u002Fcode>, Claude Code tab. On macOS, \u003Ccode class=\"key\">Ctrl\u003C\u002Fcode> becomes \u003Ccode class=\"key\">⌘\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Click “+ Add a project” to open the “New project” window. The \u003Ca href=\"\u002Fen\u002Fdocs\u002Fquick-start\u002F\">quick start\u003C\u002Fa> describes it field by field and goes all the way to the first commit.\u003C\u002Fli>\n\u003Cli>Escouade also asks, in a “Help improve Escouade?” dialog, whether it may send anonymous usage statistics: “Share statistics” or “No thanks”. Nothing is sent before you answer. The detail is on the \u003Ca href=\"\u002Fen\u002Fprivacy\u002F\">Privacy\u003C\u002Fa> page, and the choice can be changed in Settings › About (see the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-about\u002F\">“About” settings\u003C\u002Fa>).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The window opens at 1440 × 900 (1000 × 600 at the minimum); Escouade then remembers its size and position. Your projects, conversations and settings are written in \u003Ccode class=\"key\">~\u002F.escouade\u002F\u003C\u002Fcode>: see \u003Ca href=\"\u002Fen\u002Fdocs\u002Fdata\u002F\">local data\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"updates\">Updates\u003C\u002Fh2>\n\u003Cp>Updates come from Escouade’s GitHub releases. The app downloads the new version in the background and installs it without an installer window. The status bar then shows “Update X ready · Restart”: you restart when you want, or Escouade restarts by itself when no agent is working and everything is saved. That setting, “Install updates automatically”, is on by default; it is in Settings › About, where “Check for updates” runs a check right away.\u003C\u002Fp>\n\u003Cp>See \u003Ca href=\"\u002Fen\u002Fdocs\u002Fupdates\u002F\">updates\u003C\u002Fa> and the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-about\u002F\">“About” settings\u003C\u002Fa>.\u003C\u002Fp>\n",[8,12,16,19,22,25,28,31,34,37],{"id":9,"text":10,"depth":11},"requirements","Requirements",2,{"id":13,"text":14,"depth":15},"where-escouade-looks-for-claude-code","Where Escouade looks for Claude Code",3,{"id":17,"text":18,"depth":11},"installing-escouade","Installing Escouade",{"id":20,"text":21,"depth":15},"windows","Windows",{"id":23,"text":24,"depth":15},"macos","macOS",{"id":26,"text":27,"depth":15},"linux","Linux",{"id":29,"text":30,"depth":11},"claude-code-in-wsl","Claude Code in WSL",{"id":32,"text":33,"depth":11},"the-path-on-macos","The PATH on macOS",{"id":35,"text":36,"depth":11},"first-launch","First launch",{"id":38,"text":39,"depth":11},"updates","Updates",1791926756085]