Petr Houška
e509d7edc7
The Quickstart only showed the macOS/Linux `curl` installer, even though `install.ps1` installs Pi the same way: a managed install pinned by the published lockfile, updated with `pi update`. This PR adds the Windows installer as a second tab next to the existing one. All other sections stay the same. ````markdown Install Pi with the installer on macOS, Linux, or Windows: ```bash tab="macOS / Linux" curl -fsSL https://pi.dev/install.sh | sh ``` ```powershell tab="Windows" powershell -c "irm https://pi.dev/install.ps1 | iex" ``` Both installers pin all dependencies and update Pi with `pi update`. ... ```` The tabs are labelled by platform rather than by shell: newcomers know their OS, and the command also works when pasted into cmd. Tab rendering on pi.dev comes from earendil-works/pi.dev#183. This PR can merge before or after it. Until the renderer ships, and on GitHub, the page shows two ordinary code blocks, and the prose still reads correctly. ## Screenshots (with earendil-works/pi.dev#183) | | Default | Windows tab selected | |---|---|---| | Dark |  |  | | Light |  |  |
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