Interactive sessions now use the same Bash selection as Pi's shell tool, so you can use consistent command syntax across both tools. Windows sessions find Git Bash instead of falling back to cmd.exe, and Pi's shellPath setting lets you choose your Bash executable. Generated commands preserve quotes and shell symbols in prompts and watched paths. On macOS and Linux, new sessions now default to Pi's Bash selection rather than your usual shell.
Highlights
- Use consistent Bash syntax in Pi's shell tool and interactive sessions, including on Windows.
- Choose your Bash executable with Pi's
shellPathsetting. - Keep quotes and shell symbols intact in prompts and watched paths.
Need to know
| If you use… | What changes |
|---|---|
| zsh or fish as your Unix default shell | New sessions use Pi's Bash selection. Invoke zsh or fish explicitly for shell-specific syntax. |
| A legacy WSL stdin-only Bash launcher | Select Git Bash through shellPath instead; stdin-only launchers are not supported.
|
Full changelog
Highlights
- Use the same Bash command syntax in Pi's shell tool and interactive sessions, including on Windows.
- Choose your Bash executable with Pi's
shellPathsetting. - Pass prompts and watched paths containing quotes or shell symbols without changing their contents.
Changed
- New sessions and monitor detectors follow Pi's Bash selection and
shellPath. Trusted project settings can override the global setting. - On macOS and Linux, new sessions default to Pi's Bash selection instead of
$SHELL. Invoke zsh or fish explicitly when you need their syntax. - Legacy WSL stdin-only Bash launchers now report a clear error with guidance to select Git Bash.
Fixed
- Windows sessions discover Git Bash instead of defaulting to
cmd.exe, so Bash commands work consistently across Pi's tools. Thanks to @lazyst for #51. - Generated spawn and monitor commands preserve literal quotes and shell symbols. Monitor detectors use the selected Bash executable while still receiving event data as JSON on standard input.