Pi, the coding agent, compiled ahead of time to one native executable

Pi-Bolt 1.0.0, a build of the Pi coding agent compiled ahead of time to a single native executable, launches as one binary for Linux x86-64 and ARM64, macOS on Apple silicon and Windows x64 with no JIT and no Node.js or Bun required. Benchmarked against Pi 1.4.0 on Node 24 on Linux x86-64 with one CPU, Pi-Bolt is ready to type in 41 ms versus 423 ms, writes a 400 KB file through a tool call in 1.2 s versus 143.7 s, uses 2.3 s of CPU versus 18.6 s while a long answer streams, and holds 117 MB versus 521 MB of memory after 40 prompts. Pi-Bolt keeps the same commands, sessions, settings, providers and extensions as Pi, installs alongside it as pi-bolt, and offers an optional JIT build for heavy plugins that stays within about 5% of the default build's performance for Pi itself.

The Pi https://github.com/earendil-works/pi coding agent, compiled ahead of time to native code. One executable for Linux x86-64 and ARM64, macOS on Apple silicon and Windows x64. No JIT, no Node.js or Bun required. Install quick-start · Benchmarks benchmarks · Docs documentation · Website Pi-Bolt is the Pi you already use, with the same commands, sessions, settings, providers and extensions, but every function is compiled to machine code when the executable is built, so nothing is parsed or JIT-compiled at launch. Against Pi as released on Node 24, it writes a 400 KB file 120 times faster, uses 8 times less CPU while a long answer streams, 7 times less over a session and a quarter of the memory; against Pi on stock Bun, much the same. pi-bolt-v5-github.mp4 | | Pi on Node 24 | Pi‑Bolt | |---|---|---| | Ready to type | 423 ms | 41 ms <sub 10× sooner</sub | | Writing a 400 KB file through a tool call | 143.7 s | 1.2 s <sub 120× faster</sub | | CPU while a long answer streams | 18.6 s | 2.3 s <sub 8× less</sub | | CPU per prompt, 40 prompts into a session | 352 ms | 46 ms <sub 7.7× less</sub | | Memory after 40 prompts | 521 MB | 117 MB <sub 4.5× less</sub | <sub Pi-Bolt 1.0.0 against Pi 1.4.0 as released, Linux x86-64, one CPU. Every platform: Benchmarks benchmarks .</sub - Nothing to install first: one executable; no Node.js, Bun or npm to run it. - The same Pi: same commands, sessions, settings and providers; every Pi extension works unchanged. - Long sessions stay fast: a frame costs about the same with 4,000 messages as with none, and typing stays responsive. - Everywhere: Linux x86-64 and ARM64 Android too, in Termux , macOS on Apple silicon, Windows x64. Linux, macOS, Android Termux curl -fsSL https://pi-bolt.opensec.in/install.sh | sh Windows PowerShell irm https://pi-bolt.opensec.in/install.ps1 | iex Or: - Command Prompt: powershell -c "irm https://pi-bolt.opensec.in/install.ps1 | iex" - npm: npm install -g --allow-scripts=pi-bolt pi-bolt - Bun: bun add -g --trust pi-bolt - Arch Linux: the community AUR package pi-bolt-avx2-bin-release-git https://aur.archlinux.org/packages/pi-bolt-avx2-bin-release-git the x86-64 AVX2 build, signature checked , paru -S pi-bolt-avx2-bin-release-git Then, in your project: pi-bolt start pi-bolt update install the latest release pi-bolt update --rollback put back the build it replaced pi-bolt update --channel beta take pre-releases too New to Pi? Run /login to connect a provider. Your Pi configuration in ~/.pi/agent is used as is. Pi-Bolt installs next to Pi as pi-bolt , so both can stay installed; running the installer again updates, reinstalls or uninstalls it. Optional extensions the installer offers The installer verifies the release signature and offers three optional extensions by OpenSec: - opensec-pi-subagents https://www.npmjs.com/package/opensec-pi-subagents : specialized agents in separate sessions, parallel workflows and scheduled jobs. - opensec-pi-todo https://www.npmjs.com/package/opensec-pi-todo : a todo list for the model, shown as a live panel above the editor. - opensec-pi-fff https://www.npmjs.com/package/opensec-pi-fff : pi-fff's fast fuzzy find, grep and @ -mentions, at full speed on the default build. JIT build, for heavy plugins The default build has no JIT: Pi's own code is compiled machine code, and an extension loaded at run time is interpreted. Light extensions don't notice. For extensions that do heavy work search, parsing or use bun:ffi , install the JIT build. Pi itself stays compiled, so it is within about 5% of the default. macOS, Linux ARM64, Termux curl -fsSL https://pi-bolt.opensec.in/install.sh | PIBOLT VARIANT=arm64-jit sh Linux x86-64 curl -fsSL https://pi-bolt.opensec.in/install.sh | PIBOLT VARIANT=x64-jit sh On Windows, run $env:PIBOLT VARIANT = "x64-jit" before the PowerShell command. With npm, keep PIBOLT VARIANT set in your shell profile; it is read on every run. pi-bolt --version then ends in JIT on , and pi-bolt update keeps the build you chose. On the default build, an extension that needs the JIT it calls into a native library through bun:ffi fails with a line that names the extension and gives the command that switches to the JIT build. Manual download Download a build from the latest release https://github.com/opensec-git/Pi-Bolt/releases/latest , check it against SHA256SUMS , unpack it and run ./pi on Windows, pi-bolt.exe . | Download | For | |---|---| | pi-bolt-linux-x64.tar.xz | Linux , CPUs with AVX2 Intel Haswell, AMD Zen and later | | pi-bolt-linux-x64-baseline.tar.xz | Linux, any x86-64 CPU | | pi-bolt-linux-arm64.tar.xz | Linux ARM64, any 64-bit ARM CPU Raspberry Pi 3 and later, AWS Graviton, Ampere | | pi-bolt-darwin-arm64.tar.xz | macOS , Apple silicon | | pi-bolt-win32-x64.zip | Windows x64; compiled code on CPUs with AVX2, bytecode on others | -jit builds are for heavy use of plugins loaded at run time; the runtime and kit archives are what pi-bolt compile builds with compiling plugins in https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/PLUGINS.md . In Termux, use the installer: it sets the executable's loader to Termux's glibc Android android-termux . Android Termux In Termux https://termux.dev from F-Droid or GitHub the Google Play version has no glibc packages , run the same curl ... | sh command. Pi-Bolt is a glibc program and Android's libc is not glibc, so the installer first installs Termux's glibc pkg install glibc-repo && pkg install glibc , after asking , sets it as the executable's loader, and links pi-bolt into $PREFIX/bin . pi-bolt is a small launcher that starts Pi-Bolt in Android's time zone and without Termux's LD PRELOAD a library of Android's libc, which glibc cannot load ; the programs Pi-Bolt starts get it back. The installer copies Termux's resolv.conf and hosts to $PREFIX/glibc/etc , where Termux's glibc reads them. Requirements - Linux x86-64 or ARM64 with glibc 2.17 or later Ubuntu 20.04+, Debian 11+, RHEL/Rocky 8+, Amazon Linux 2, Raspberry Pi OS 64-bit . musl is not supported. - Android 7 or later on 64-bit ARM, in Termux. - macOS 13 or later on Apple silicon. Install with the installer or npm Troubleshooting https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/TROUBLESHOOTING.md macos . - Windows 10 1809 or later, or Windows 11, on x64. Install with the installer or npm; for problems, see Troubleshooting: Windows https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/TROUBLESHOOTING.md windows . - Windows on ARM64 runs the x64 build, in Windows 11's x64 emulation. - Editors: pi-bolt --acp runs Pi-Bolt in the agent panel of Zed, JetBrains IDEs, VS Code, Neovim and other ACP https://agentclientprotocol.com editors, with your Pi settings, extensions, skills and sessions. Setup https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/ACP.md - Other agents: pi-bolt --mcp is an MCP https://modelcontextprotocol.io server; other agents give Pi-Bolt a task with its prompt tool and continue the session in later calls. Setup https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/MCP.md - Built-in search: the grep and find tools are on by default and search in-process, following .gitignore , with nothing to install. With opensec-pi-fff https://www.npmjs.com/package/opensec-pi-fff or @ff-labs/pi-fff loaded, FFF's search tools are used instead. - Compiled plugins: pi-bolt compile compiles the extensions installed on this machine into your Pi-Bolt Linux and macOS with the release's own compiler, where they run as machine code; pi-bolt update compiles them into each new release. Plugins https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/PLUGINS.md - Doctor: pi-bolt doctor prints a plain-text report of your installation to paste into an issue. Details pi-bolt-doctor - Updates: pi-bolt update installs the latest release, and --rollback puts back the build it replaced. - Herdr: Pi-Bolt shows its state in a Herdr https://herdr.dev pane, and a Herdr restart reopens the conversation. Details herdr - ARM64 and Android: Linux ARM64 builds, and the same installer in Termux. Android android-termux Pi extensions work unchanged. The default build has no JIT, so an extension loaded at run time is interpreted; compile the ones you use every day into Pi-Bolt with pi-bolt compile , or use the JIT build jit-build-for-heavy-plugins . Setup in Zed and Claude Code In Zed's settings.json other editors https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/ACP.md : "agent servers": { "Pi-Bolt": { "type": "custom", "command": "/full/path/to/pi-bolt", "args": "--acp" , "env": {} } } In Claude Code other clients https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/MCP.md : claude mcp add pi-bolt -- /full/path/to/pi-bolt --mcp Pi and Pi-Bolt side by side Pi-Bolt uses Pi's agent directory ~/.pi/agent and shared packages list. Ordinary pi-bolt install and pi-bolt remove update that shared list, just as Pi does, and drop Pi-Bolt's own entry for that package, so both load what the shared list declares. Add --pi-bolt to change only Pi-Bolt's overrides. Using fictional package names: pi-bolt install --pi-bolt npm:@example/bolt-tools pi-bolt remove --pi-bolt npm:@example/shared-tools piBolt.packages extends the shared list. A -source entry excludes an inherited package from Pi-Bolt without changing Pi; other shared packages remain inherited. See Configuration https://pi-bolt.opensec.in/docs/configuration.html . { "packages": "npm:@juicesharp/rpiv-todo" , "piBolt": { "packages": "-npm:@juicesharp/rpiv-todo", "npm:opensec-pi-todo" } } pi-bolt doctor pi-bolt doctor prints a report of your installation, in plain text to paste into an issue: the build and how it was installed, whether the release's signature verifies, which extensions are compiled in, run at run time or fail to load, how Pi's packages and piBolt.packages differ, the Herdr and editor setup, and the problems it finds, such as another pi-bolt earlier on your PATH . It prints no keys or tokens, and shows your home folder as ~ . pi-bolt doctor --offline leaves out the release signature and the check for a newer version. Herdr In a Herdr https://herdr.dev pane, Pi-Bolt shows up as pi-bolt idle, working or blocked , and a Herdr restart reopens the same conversation in the same pane. There is nothing to install; "-builtin:herdr" in the extensions setting turns it off. Restoring a session needs Herdr 0.9.2 or later. To start other agents in Herdr panes from Pi-Bolt, install pi-herdr https://www.npmjs.com/package/@andrewjacop/pi-herdr : pi-bolt install npm:@andrewjacop/pi-herdr . Pi-Bolt 1.0.0 against Pi 1.4.0 as released on npm, run by stock Bun 1.4.4 and by Node 24, doing the same work against the same local model; lower is better. Linux x86-64 | Benchmark | Pi-Bolt | Pi on Bun | Pi on Node 24 | |---|---|---|---| | Writing a 400 KB file through a tool call, s | 1.2 | 194.8 | 143.7 | | CPU, streaming a 60,000-character answer, s | 2.34 | 21.92 | 18.62 | | CPU per prompt, prompts 21 to 40 of a session, ms | 46 | 328 | 352 | | CPU, interactive session, ms | 167 | 1,087 | 1,180 | | Memory after 40 prompts, MB | 117 | 309 | 521 | | Ready to type, ms | 41 | 366 | 423 | Linux ARM64 | Benchmark | Pi-Bolt | Pi on Bun | Pi on Node 24 | |---|---|---|---| | Writing a 400 KB file through a tool call, s | 1.3 | 164.1 | 134.5 | | CPU, streaming a 60,000-character answer, s | 2.32 | 18.82 | 18.19 | | CPU per prompt, prompts 21 to 40 of a session, ms | 42 | 280 | 299 | | CPU, interactive session, ms | 156 | 1,021 | 1,099 | | Memory after 40 prompts, MB | 120 | 299 | 640 | | Ready to type, ms | 37 | 334 | 390 | macOS Apple M5 | Benchmark | Pi-Bolt | Pi on Bun | Pi on Node 24 | |---|---|---|---| | Writing a 400 KB file through a tool call, s | 0.6 | 76.2 | 96.7 | | CPU, streaming a 60,000-character answer, s | 1.35 | 7.10 | 6.47 | | CPU per prompt, prompts 21 to 40 of a session, ms | 17 | 111 | 149 | | CPU, interactive session, ms | 80 | 485 | 523 | | Memory after 40 prompts, MB | 89 | 746 | 1,363 | | Ready to type, ms | 24 | 120 | 151 | Windows x64 | Benchmark | Pi-Bolt | Pi on Bun | Pi on Node 24 | |---|---|---|---| | Writing a 400 KB file through a tool call, s | 1.8 | 131.0 | 110.1 | | CPU, streaming a 60,000-character answer, s | 2.69 | 44.86 | 39.01 | | CPU per prompt, prompts 21 to 40 of a session, ms | 53 | 278 | 379 | | CPU, interactive session, ms | 213 | 1,266 | 1,286 | | Memory after 40 prompts, MB | 79 | 286 | 378 | | Ready to type, ms | 78 | 300 | 363 | GitHub's runners for Linux pinned to one CPU and Windows 2 cores; memory there is the working set ; macOS on an Apple M5, not pinned. Node 22, the method and the raw data: bench/results/2026-10-23-stock-bun-1.0.0 https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/bench/results/2026-10-23-stock-bun-1.0.0 . Against PiG https://github.com/MichaelKinsy/PiG 0.5.1 Pi ported to Go : Pi-Bolt against PiG https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/BENCHMARKS.md 100-against-pig-051-and-099 . Every other result, and the method: docs/BENCHMARKS.md https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/BENCHMARKS.md . 1. Bun bundles Pi and compiles it to JavaScriptCore bytecode. 2. An ahead-of-time compiler turns every function into optimized x86-64 or ARM64 machine code, through B3, the back end of JavaScriptCore's top-tier JIT. 3. A prebuilt heap holds Pi's modules already loaded, and is mapped from the executable at launch. 4. A training profile orders the code so that startup touches as few pages as possible. Diagram and sources The compiler builds on oven-sh/WebKit 743 https://github.com/oven-sh/WebKit/pull/743 . Pi-Bolt ports it to x86-64 and macOS and adds its own code generation and runtime work docs/ARCHITECTURE.md https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/ARCHITECTURE.md . packages/ is the Pi release named in sources.json https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/sources.json with Pi-Bolt's changes on top; the engine changes are in patches/ . - Architecture https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/ARCHITECTURE.md : what the executable contains, how it is built, what happens at launch - Building https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/BUILDING.md : building the runtime and Pi from source, training profiles, tests - Benchmarks https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/BENCHMARKS.md : method, results and raw data - Plugins https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/PLUGINS.md : porting Pi extensions and writing them for AOT - Editors https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/ACP.md : Pi-Bolt in Zed, JetBrains IDEs, VS Code and other ACP editors - Other agents https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/MCP.md : Pi-Bolt as a tool of other agents and MCP clients - Troubleshooting https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/TROUBLESHOOTING.md : diagnostics, environment variables, known limitations - Releasing https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/docs/RELEASING.md : CI, releases, signing Bug reports, benchmarks on other hardware and fixes are welcome: see CONTRIBUTING.md https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/CONTRIBUTING.md . Report security issues privately, as described in SECURITY.md https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/SECURITY.md . Build from source git clone https://github.com/opensec-git/Pi-Bolt.git && cd Pi-Bolt scripts/fetch-runtime.sh the released Pi-Bolt runtime or build it: docs/BUILDING.md scripts/prepare-pi.sh builds the Pi in this repository scripts/build-pi.sh out/pi-bolt/pi tests/aot/run.sh engine tests MIT. Release executables include Bun MIT , JavaScriptCore LGPL-2.0 and BSD , ICU Unicode License and Pi MIT ; see THIRD PARTY NOTICES.md https://github.com/opensec-git/Pi-Bolt/blob/pi-bolt/THIRD PARTY NOTICES.md . Note Pi-Bolt is an independent fork of Pi https://github.com/earendil-works/pi , not affiliated with Pi's authors or with Oven. Built on Pi https://github.com/earendil-works/pi by Mario Zechner and contributors, and Bun https://github.com/oven-sh/bun by Oven.