First release of Pi-Bolt: Pi 1.0.0, compiled ahead of time to native x86-64 code, as one self-contained Linux executable.
Highlights (vs Pi on Bun 1.4.2 / Node 22)
| Pi-Bolt | Bun 1.4.2 | Node 22 | |
|---|---|---|---|
| Interactive launch, ready to type | 77 ms | 123 ms | 305 ms |
| CPU, 5-prompt interactive session | 378 ms | 827 ms | 1,235 ms |
pi -p, one prompt with 4 tool calls
| 112 ms | 164 ms | 406 ms |
| Per prompt late in a 2.7M-token session | 154 ms | 232 ms | 249 ms |
Methodology and every figure: docs/BENCHMARKS.md.
Install
curl -fsSL https://pi-bolt.opensec.in/install.sh | shOr pick an archive below, check it with sha256sum -c --ignore-missing SHA256SUMS, unpack it, and run ./pi.
| Asset | For |
|---|---|
pi-bolt-linux-x64.tar.gz
| Recommended. CPUs with AVX2 (Intel Haswell 2013+, AMD Zen+). |
pi-bolt-linux-x64-baseline.tar.gz
| Any x86-64 CPU. |
pi-bolt-linux-x64-jit.tar.gz
| JIT also on, for code loaded at run time (run-time plugins). |
pi-bolt-runtime-linux-x64.tar.gz
| The Pi-Bolt Bun runtime, for compiling plugins in (docs/PLUGINS.md). |
Linux x86-64 with glibc 2.17 or later. Tested on Ubuntu 20.04/22.04/24.04, Debian 11/12, Rocky Linux 8/9, CentOS 7 and Amazon Linux 2.
Notes
- Pi itself is unmodified. Its end-to-end tool output is byte-identical to Pi on stock Bun.
- Plugins (Pi extensions) work unchanged. Compile them in with
scripts/build-pi.sh --pluginsto run them as native code. - Known gap: while a reply streams, CPU is 5–15% above a fully warmed-up JIT. Whole sessions use less than half of Bun's CPU.