081a6e87f6
`FileAuthStorageBackend` locked `auth.json` with proper-lockfile and `realpath: false`, so the lock directory was `<path as given>.lock`. Reads and writes follow symlinks to the same real file, but each path alias got its own lock. For example, an agent dir whose `auth.json` is a symlink to a shared file used a different lock than the real file. Two pi processes could then enter the credential-modification section at the same time and refresh the same OAuth token concurrently. This change drops `realpath: false` from the sync and async lock calls, so proper-lockfile resolves the path and every alias of the file uses one lock. Resolving the path needs the file to exist, which is already the case: `ensureFileExists()` runs before either lock is taken. The same `realpath: false` pattern is also in `settings-manager.ts`, `trust-manager.ts`, and `package-manager-cli.ts`. This change leaves those alone. ## Testing - I added a test to `test/auth-storage.test.ts`. It holds the lock on the real `auth.json`, then checks that a backend opened through a symlink alias waits in `withLockAsync` until aborted, and gets `ELOCKED` from `withLock`. Neither path runs the mutation. Without the fix the test fails because the async call enters the lock; with the fix it passes. - `node ../../node_modules/vitest/dist/cli.js --run test/auth-storage test/settings`: 151 tests pass. - `npm run check` passes. - With the reproduction script from the issue, current main prints `symlink alias: ENTERED`; with this change it prints `symlink alias: BLOCKED`. The same-path control prints `BLOCKED` in both cases. Fixes #11655 Requested by @badlogic Co-authored-by: triagent <triagent@localhost> Co-authored-by: Mario Zechner <contact@badlogicgames.com> |
||
|---|---|---|
| .. | ||
| 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