b2cb629237
Fixes #11692. ## Problem In RPC mode the startup catalog refresh runs in the background and also refreshes an expired OAuth credential. If pi exits after the token request went out but before the new token is written, the provider has already spent the old single-use refresh token and auth.json keeps only that one. The next request fails with `invalid_grant`. Trace: `pi --mode rpc` starts, `get_state` is answered, catalog refresh sends the token request, the client sends SIGTERM (or closes stdin), `shutdown()` runs `runtimeHost.dispose()`, which does not know about the refresh, and the process exits. Same for print and interactive mode, and for a prompt-time refresh cut off by an exit. ## Fix - `RuntimeCredentials.modify()` tracks every pending modification (same idiom as the MCP `track()` / `McpAuthProvider.settled()`). - `RuntimeCredentials.settled()` / `ModelRuntime.settleCredentialWrites()` wait for them. - `AgentSessionRuntime.dispose()` waits for them. All modes exit through `dispose()`. No extra timeout: the OAuth refresh (15 s) and the auth.json lock wait (30 s) are already bounded, and a second signal still exits at once. Not changed: the catalog refresh still refreshes expired OAuth credentials, also for providers whose catalog does not use them (the pi.dev catalog for `openai`, `anthropic`, ...). Skipping that would need a per-provider "catalog needs auth" signal in pi-ai; it is optional now that exits wait. `docs/rpc.md` now says that pi waits for pending work before exiting. ## Testing - `test/runtime-credentials.test.ts`: `settled()` waits until a pending modification is written, and resolves after a failed one. - `test/suite/regressions/11692-dispose-waits-for-oauth-refresh.test.ts`: `dispose()` waits until the token from a background catalog refresh is saved. Fails without the fix. - Real process: `pi --mode rpc` with an extension OAuth provider (expired credential, 400 ms refresh), SIGTERM about 100 ms after the token request started. Without the wait: 3 of 3 runs kept the spent refresh token. With the fix: 3 of 3 saved the new one (exit 143). Closing stdin instead of SIGTERM: new token saved, exit 0. - `npm run check`; `test/rpc*`, `test/print-mode`, `test/model-runtime*`, runtime and regression suites pass. |
||
|---|---|---|
| .. | ||
| docs | ||
| examples | ||
| install-lock | ||
| schemas | ||
| scripts | ||
| src | ||
| test | ||
| .gitignore | ||
| CHANGELOG.md | ||
| package.json | ||
| README.md | ||
| tsconfig.build.json | ||
| tsconfig.examples.json | ||
| vitest.config.ts | ||
New issues and PRs from new contributors are closed automatically. Maintainers review closed submissions daily. See CONTRIBUTING.md.
Pi
Pi is a minimal, extensible agent harness that you can make your own.
Adapt Pi to your workflows, not the other way around. Customize Pi with extensions, skills, prompt templates, and themes. Bundle them as Pi packages and share via npm or git.
Pi ships with powerful defaults but skips features like sub-agents and plan mode. Ask Pi to build what you want, or install a package that does it your way.
Use Pi interactively, automate it in print or JSON mode, control it over RPC, or build apps with the Pi TypeScript SDK. See OpenClaw for a real-world integration.
Getting started
Install the command-line interface:
curl -fsSL https://pi.dev/install.sh | sh
On Windows:
powershell -c "irm https://pi.dev/install.ps1 | iex"
The installer pins all dependencies and updates Pi with pi update. Alternatively, install directly with npm, which does not pin transitive dependencies:
npm install -g --ignore-scripts @earendil-works/pi-coding-agent
Pi requires Node.js 22.19 or newer. The macOS, Linux, and Windows installers can install it if needed. Pi does not require dependency lifecycle scripts for a normal npm installation.
On macOS and Linux, Nix users can install the latest release with nix profile add github:earendil-works/pi/stable. See the quickstart for updating and pinning releases.
Start Pi in the directory where you want it to work:
cd /path/to/project
pi
For a built-in AI provider, run /login inside Pi to connect a subscription or API key. Then give Pi a task.
See the documentation for full setup and usage instructions.
Share your OSS coding agent sessions
If you use Pi for open source work, please share your coding agent sessions.
Public OSS session data helps improve models, prompts, tools, and evaluations using real development workflows.
For the full explanation, see this post on X.
To publish sessions, use badlogic/pi-share-hf using a Hugging Face account and the Hugging Face CLI.
- Demo video on how to publish Pi sessions
- Published Pi development sessions:
badlogicgames/pi-monoon Hugging Face.
Development
Clone the repository, install its dependencies, and run Pi from source:
git clone https://github.com/earendil-works/pi
cd pi
npm install --ignore-scripts
./pi-test.sh
pi-test.sh can be called from any directory and preserves the caller's working directory.
Before submitting changes, run:
npm run check
./test.sh
Read CONTRIBUTING.md before opening an issue or pull request. It defines the contribution gate, issue quality bar, and required checks. Read AGENTS.md for repository-specific implementation, testing, dependency, and release rules.
License
MIT