| ... | @@ -5,17 +5,34 @@ extensions, skills, context files, and native session history. | ... | @@ -5,17 +5,34 @@ extensions, skills, context files, and native session history. |
| 5 | | 5 | |
| 6 | ## Set Up Pi | 6 | ## Set Up Pi |
| 7 | | 7 | |
| 8 | 1. Install Pi on the machine running the T3 Code server. Pi 1.0 is recommended; 0.80.5 is the | 8 | 1. Install [Pi](https://pi.dev) on the machine running the T3 Code server. Pi requires Node.js |
| 9 | oldest version T3 Code supports. | 9 | 22.19 or newer; its platform installers can install Node if needed. T3 Code supports Pi |
| 10 | 2. Run Pi once in a terminal and finish the provider login or API-key setup you normally use. | 10 | 0.80.5 or newer. |
| | 11 | 2. Run `pi` in a terminal, then `/login` to connect your model provider or configure its API key. |
| 11 | 3. Open T3 Code Settings, enable Pi, and refresh the provider. | 12 | 3. Open T3 Code Settings, enable Pi, and refresh the provider. |
| 12 | | 13 | |
| | 14 | For an npm installation, use: |
| | 15 | |
| | 16 | ```sh |
| | 17 | npm install -g --ignore-scripts @earendil-works/pi-coding-agent |
| | 18 | ``` |
| | 19 | |
| 13 | If `pi` is not on the server's `PATH`, set Pi's binary path to the executable. Provider environment | 20 | If `pi` is not on the server's `PATH`, set Pi's binary path to the executable. Provider environment |
| 14 | variables and launch arguments are also available for installations that need a custom agent | 21 | variables and launch arguments are also available for installations that need a custom agent |
| 15 | directory, endpoint, or model configuration. `--provider` must be paired with `--model`. T3 Code | 22 | directory, endpoint, or model configuration. `--provider` must be paired with `--model`. T3 Code |
| 16 | rejects launch arguments that change Pi's execution mode or select a session because T3 owns those | 23 | rejects launch arguments that change Pi's execution mode or select a session because T3 owns those |
| 17 | parts of the process lifecycle. | 24 | parts of the process lifecycle. |
| 18 | | 25 | |
| | 26 | On a remote or headless server, connect to that machine over SSH and run `pi`, then `/login`. |
| | 27 | Open the authorization URL on your own computer. If the callback cannot reach the server, |
| | 28 | paste the final redirect URL or authorization code back into Pi when prompted. You can also |
| | 29 | set your model provider's API-key environment variable in the Pi instance's settings; mark |
| | 30 | secret values as sensitive. |
| | 31 | |
| | 32 | Update installer-managed Pi with `pi update`. If another package manager owns the installation, |
| | 33 | update it through that manager instead. For example, a Nix profile installation uses |
| | 34 | `nix profile upgrade pi`. |
| | 35 | |
| 19 | ## What Carries Over | 36 | ## What Carries Over |
| 20 | | 37 | |
| 21 | T3 Code discovers the models reported by Pi and exposes their supported thinking levels. The | 38 | T3 Code discovers the models reported by Pi and exposes their supported thinking levels. The |