0d23d53457
## What was wrong `pi update --extensions` first looks up the newest version of each npm package with `npm view`. If that version is newer than the installed one, pi runs `npm install <name>@latest`. The two commands read different registry documents, and each is cached separately. Shortly after a publish, `npm view` can already report the new version while `npm install` still resolves the old one. npm then exits successfully, pi prints "Updated packages", and the startup banner lists the same package again on the next launch. The user can't tell that nothing was actually updated. ## What the change does - `shouldUpdateNpmSource` now returns the installed version and the registry version along with its decision. Both are carried on `NpmUpdateTarget`. - After `npm install`, `updateNpmBatch` re-reads each package's installed version. If the registry lookup succeeded and the version did not change, it emits a `progress` event with the message: `<source> is still X (registry reports Y); npm registry metadata may be stale, try again in a few minutes`. - The package CLI now prints `progress` events in yellow. Until now nothing emitted them. Install behavior is unchanged: pi still installs `@latest`. ## Testing - New test in `test/package-manager.test.ts`: two packages are flagged for update and only one is actually upgraded. The warning is emitted only for the unchanged one. The test fails without the change. - `test/package-manager.test.ts` passes (129 tests), and `npm run check` passes. - Ran the built CLI with an `npmCommand` stub whose `view` reports `1.0.1` and whose `install` changes nothing: ``` Updating npm:demo-pkg... npm:demo-pkg is still 1.0.0 (registry reports 1.0.1); npm registry metadata may be stale, try again in a few minutes Updated packages ``` Fixes #11536 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