alexion/dev
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

chore(vendor): import pi 1.3.0

Browse Source 
Imported as a linear vendor commit so forge rebases do not replay the upstream root tree.

git-subtree-dir: third_party/pi

git-subtree-split: 71023aec1546d6d677a65669c5665c0927ce0dd0
This commit is contained in:
alexion
2026-10-15 17:58:48 -04:00
parent 719370c8f7
commit 6081e3e325
1743 changed files with 205460 additions and 131705 deletions
Download Patch File Download Diff File Expand all files Collapse all files

62
third_party/pi/packages/coding-agent/docs/windows.md vendored
View File

@@ -1,18 +1,40 @@
# Windows Setup
# Run Pi on Windows
Pi uses Git Bash by default on Windows. Checked locations (in order):
Run Pi either as a native Windows process or inside Windows Subsystem for Linux (WSL). Native Windows uses Git Bash by default for Bash commands and can optionally expose PowerShell to the model. Pi inside WSL uses the Linux environment and its Bash installation.
1. Custom path from `~/.pi/agent/settings.json`
2. Git Bash (`C:\Program Files\Git\bin\bash.exe`)
3. `bash.exe` on PATH (Cygwin, MSYS2, WSL)
Follow the main [Quickstart](quickstart.md) to install and authenticate Pi. Use this page to choose and configure its command environment.
For most users, [Git for Windows](https://git-scm.com/download/win) is sufficient.
## Choose native Windows or WSL
## PowerShell Tool
| Environment | Command environment | Use it when |
|---|---|---|
| Native Windows with Git Bash | Git Bash for the built-in `bash` tool and `!` commands | Your files and development tools primarily live on Windows |
| Native Windows with the `powershell` tool | PowerShell for model tool calls; Bash remains available for `!` commands | The task depends on PowerShell modules or Windows-native commands |
| WSL | Linux Bash and tools inside the selected WSL distribution | Your files and toolchain already live in Linux or WSL |
The optional `powershell` tool runs commands through `pwsh.exe` when available, otherwise Windows PowerShell. It starts PowerShell with `-NoProfile -NonInteractive -ExecutionPolicy Bypass`. Administrator-enforced execution policies can still take precedence.
## Use Git Bash on native Windows
Use `defaultTools` to replace the model-facing `bash` tool:
For most native Windows users, installing [Git for Windows](https://git-scm.com/download/win) is sufficient.
Pi resolves Bash in this order:
1. `shellPath` from `~/.pi/agent/settings.json`
2. Git Bash under `Program Files` or `Program Files (x86)`
3. `bash.exe` on `PATH`, including Cygwin, MSYS2, or legacy WSL Bash
Start Pi and enter this command to verify the shell:
```text
!printf 'Bash is working\n'
```
If Pi cannot find Bash, it reports the locations it checked. Install Git for Windows, put another Bash executable on `PATH`, or configure `shellPath`.
## Let the model use PowerShell
The optional `powershell` tool runs commands through `pwsh.exe` when available, then falls back to Windows PowerShell. It starts PowerShell with `-NoProfile -NonInteractive -ExecutionPolicy Bypass`. Administrator-enforced execution policies can still take precedence.
To replace the model-facing `bash` tool with `powershell`, add this to `~/.pi/agent/settings.json`:
```json
{
@@ -20,20 +42,26 @@ Use `defaultTools` to replace the model-facing `bash` tool:
}
```
Or enable both while comparing behavior:
`["-bash", "+powershell"]` does the same while keeping any other default tools you configured.
```json
{
"defaultTools": ["read", "bash", "powershell", "edit", "write"]
}
```
Restart Pi, then ask it to run a harmless PowerShell command. The `!` and `!!` editor commands continue to use Bash. The `powershell` tool is available only when Pi runs as a native Windows process.
The `!` and `!!` editor commands still use Bash.
See [Settings](settings.md#tools) for other tool combinations.
## Custom Bash Path
## Use a custom Bash executable
Set `shellPath` when Bash is installed somewhere Pi does not discover automatically:
```json
{
"shellPath": "C:\\cygwin64\\bin\\bash.exe"
}
```
JSON uses backslashes for escape sequences. When you write a Windows path with backslashes, write each backslash twice, as shown above.
See [Configure shell commands](shell-aliases.md) for command prefixes, aliases, and the complete shell-resolution behavior.
## Configure Windows Terminal
Windows Terminal reserves or rewrites some modified keys. See [Windows Terminal](terminal-setup.md#windows-terminal) to configure `Shift+Enter` and `Alt+Enter`, and [Keybindings](keybindings.md) for Pi's Windows and WSL shortcut defaults.