807a5c051f
When writing a session entry failed (ENOSPC, EBUSY, ETIMEDOUT on network drives), `SessionManager._appendEntry` had already added the entry to memory and made it the current leaf. The process kept running, and the next entry written to disk pointed to a parent that was not in the file. On resume, pi follows the history only back to that gap: everything before it disappears. In #11460 that also dropped the first system message, which declares the tools, so resume turned off every built-in tool. `_appendEntry` now undoes the in-memory append if writing fails, then rethrows. The error reaches the caller as before; later entries chain to the last entry actually on disk. Reports of this problem: - #11460: ENOSPC; resume dropped all built-in tools. - #10166: failure injected with EBUSY; the next entry on disk points to a missing parent. - #10661: ETIMEDOUT on Windows + NFS; resumed sessions showed only the last few messages. That report also describes NUL holes in the file, which this change does not address. **Testing** - Two tests in `test/session-manager/file-operations.test.ts` make writes fail with real file permissions: a read-only session file (failed append) and a read-only session directory (failed first file creation). They check that the entry is not kept, the leaf is unchanged, the next entry chains to the last written one, and the reopened session's branch contains both entries. Both fail without the change and pass with it. - `test/session-manager/` and `test/default-tools-setting.test.ts` pass (140 tests). - `npm run check` passes. Fixes #11460 Requested by @davidbrai Co-authored-by: triagent <triagent@localhost> |
||
|---|---|---|
| .. | ||
| 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