[{"data":1,"prerenderedAt":31},["ShallowReactive",2],{"doc:en:settings-terminals":3},{"title":4,"lede":5,"html":6,"headings":7},"Settings: Terminals","The “Terminals” tab of the settings tells Escouade where to find the shells used by the built-in terminals, launch commands, worktree commands, and tests.","\u003Ch2 id=\"open-the-tab\">Open the tab\u003C\u002Fh2>\n\u003Cp>Open the settings with \u003Ccode class=\"key\">Ctrl+,\u003C\u002Fcode> (\u003Ccode class=\"key\">⌘,\u003C\u002Fcode> on macOS), then choose “Terminals” (“Shells available in the built-in terminals”). These are the app’s settings, shared by all projects; they apply on “Save”. The terminals themselves are described in \u003Ca href=\"\u002Fen\u002Fdocs\u002Fterminals\u002F\">terminals\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>The tab has a single group, “Paths”. Escouade detects shells on its own; you only fill in a field to point to a shell it can’t find, or to prefer another one.\u003C\u002Fp>\n\u003Ch2 id=\"paths\">Paths\u003C\u002Fh2>\n\u003Cp>Under the group’s title, the “Detected:” line lists the shells found, for example “Detected: PowerShell, Git Bash, WSL”, or “Detected: none”. It updates once the settings are saved.\u003C\u002Fp>\n\u003Cp>On Windows, the tab has three fields:\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>“PowerShell 7”\u003C\u002Ftd>\n\u003Ctd>The path to \u003Ccode class=\"key\">pwsh.exe\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003Ctd>Empty (“blank = auto”)\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Git Bash”\u003C\u002Ftd>\n\u003Ctd>The path to \u003Ccode class=\"key\">bash.exe\u003C\u002Fcode>, the bash of Git for Windows.\u003C\u002Ftd>\n\u003Ctd>Empty (“blank = auto”)\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“WSL distribution”\u003C\u002Ftd>\n\u003Ctd>The name of the WSL distribution to use, for example \u003Ccode class=\"key\">Ubuntu\u003C\u002Fcode>.\u003C\u002Ftd>\n\u003Ctd>Empty (“blank = default distribution”)\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>On macOS, the tab has a single field, “bash” (“blank = auto”), for the path to bash.\u003C\u002Fp>\n\u003Cdiv class=\"callout note\">\u003Cp class=\"callout-title\">Note\u003C\u002Fp>\u003Cp>On Linux, the tab shows the same three fields as on Windows, but only the “Git Bash” field counts: it then points to \u003Ccode class=\"key\">bash\u003C\u002Fcode>. The “PowerShell 7” and “WSL distribution” fields have no effect there.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Cp>An empty field lets Escouade search. A path that points to no file isn’t replaced by detection: the matching shell isn’t offered. For PowerShell, Escouade then falls back to Windows PowerShell if it’s installed.\u003C\u002Fp>\n\u003Ch2 id=\"how-shells-are-detected\">How shells are detected\u003C\u002Fh2>\n\u003Ch3 id=\"on-windows\">On Windows\u003C\u002Fh3>\n\u003Cp>Shells are listed in this order:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>PowerShell\u003C\u002Fstrong>: the path in the “PowerShell 7” field if it’s filled in. Otherwise \u003Ccode class=\"key\">pwsh.exe\u003C\u002Fcode> in the \u003Ccode class=\"key\">PATH\u003C\u002Fcode>, then the \u003Ccode class=\"key\">PowerShell\\7\u003C\u002Fcode> and \u003Ccode class=\"key\">PowerShell\\7-preview\u003C\u002Fcode> folders of Program Files, then the Microsoft Store alias (\u003Ccode class=\"key\">WindowsApps\\pwsh.exe\u003C\u002Fcode>). Without PowerShell 7, Windows PowerShell (\u003Ccode class=\"key\">powershell.exe\u003C\u002Fcode>, shipped with Windows) is offered instead, as “Windows PowerShell”.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Git Bash\u003C\u002Fstrong>: the path in the “Git Bash” field if it’s filled in. Otherwise the \u003Ccode class=\"key\">bash.exe\u003C\u002Fcode> in Git’s folder, found from \u003Ccode class=\"key\">git.exe\u003C\u002Fcode> in the \u003Ccode class=\"key\">PATH\u003C\u002Fcode> (\u003Ccode class=\"key\">bin\\bash.exe\u003C\u002Fcode> or \u003Ccode class=\"key\">usr\\bin\\bash.exe\u003C\u002Fcode>), then \u003Ccode class=\"key\">Git\\bin\\bash.exe\u003C\u002Fcode> in Program Files.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WSL\u003C\u002Fstrong>: offered as soon as \u003Ccode class=\"key\">wsl.exe\u003C\u002Fcode> exists. It’s named “WSL”, or “WSL (Ubuntu)” with the distribution from the “WSL distribution” field. The terminal opens in the right folder, in that distribution; with the field empty, it’s WSL’s default distribution.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3 id=\"on-macos-and-linux\">On macOS and Linux\u003C\u002Fh3>\n\u003Cp>The login shell (the \u003Ccode class=\"key\">SHELL\u003C\u002Fcode> variable) comes first if it’s zsh, bash, fish, or sh, then zsh, bash, and fish, searched in \u003Ccode class=\"key\">\u002Fbin\u003C\u002Fcode>, \u003Ccode class=\"key\">\u002Fusr\u002Fbin\u003C\u002Fcode>, and the \u003Ccode class=\"key\">PATH\u003C\u002Fcode>. \u003Ccode class=\"key\">sh\u003C\u002Fcode> is only offered if no other shell is found. The “bash” field overrides where bash is, except when \u003Ccode class=\"key\">SHELL\u003C\u002Fcode> already names bash: that bash is then the one used.\u003C\u002Fp>\n\u003Ch2 id=\"which-shell-is-used-for-what\">Which shell is used for what\u003C\u002Fh2>\n\u003Cp>The order of the list matters: there’s no “default shell” setting, it’s the first shell detected.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>In the sidebar, the \u003Cstrong>+\u003C\u002Fstrong> button of the “Terminals” section (“New terminal”) opens a menu with every detected shell: you pick one.\u003C\u002Fli>\n\u003Cli>“Open a terminal” (an agent’s menu) and “Open a terminal here” (the editor’s file tree menu) use the first shell.\u003C\u002Fli>\n\u003Cli>A launch command or a worktree command has its own “Shell” choice, in the project’s settings (see the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-projects\u002F\">“Projects”\u003C\u002Fa> tab). A new command starts with the first shell. See \u003Ca href=\"\u002Fen\u002Fdocs\u002Flaunch\u002F\">launch\u003C\u002Fa> and \u003Ca href=\"\u002Fen\u002Fdocs\u002Fworktrees\u002F\">worktrees\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>The Kanban’s “Test command” (the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-board\u002F\">“Kanban”\u003C\u002Fa> tab) and test launches (\u003Ca href=\"\u002Fen\u002Fdocs\u002Ftesting\u002F\">testing\u003C\u002Fa>) also use the first shell.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>With no shell detected, the \u003Cstrong>+\u003C\u002Fstrong> button shows “No shell found (PowerShell 7, Git Bash, WSL). Check the settings.”\u003C\u002Fp>\n\u003Ch2 id=\"what-is-set-elsewhere\">What is set elsewhere\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>The proxy in terminals\u003C\u002Fstrong>: “Also apply the proxy to the built-in terminals” is in the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-network\u002F\">“Network”\u003C\u002Fa> tab. It also applies to launch and worktree commands.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Claude Code in WSL\u003C\u002Fstrong>: on Windows, when the executable path (the \u003Ca href=\"\u002Fen\u002Fdocs\u002Fsettings-claude-code\u002F\">“Claude Code”\u003C\u002Fa> tab) is empty and no \u003Ccode class=\"key\">claude\u003C\u002Fcode> is found on Windows, Escouade looks for one installed in WSL, in the distribution from the “WSL distribution” field (the default distribution if it’s empty).\u003C\u002Fli>\n\u003C\u002Ful>\n",[8,12,15,18,22,25,28],{"id":9,"text":10,"depth":11},"open-the-tab","Open the tab",2,{"id":13,"text":14,"depth":11},"paths","Paths",{"id":16,"text":17,"depth":11},"how-shells-are-detected","How shells are detected",{"id":19,"text":20,"depth":21},"on-windows","On Windows",3,{"id":23,"text":24,"depth":21},"on-macos-and-linux","On macOS and Linux",{"id":26,"text":27,"depth":11},"which-shell-is-used-for-what","Which shell is used for what",{"id":29,"text":30,"depth":11},"what-is-set-elsewhere","What is set elsewhere",1791926756659]