Pi-Bolt 1.3.0 is Pi 1.6.0 on 1.2.1, built ahead of
time as before, with a new engine and less work and memory in long sessions. What Pi 1.6.0 brings is in its release notes; in
short: GPT-6.2 Sol and GPT-6.2 Astra, find patterns relative to the search folder, a resume command on its own line, and fixes
to read, find, bash, /resume, /share, /export and session replacement in RPC mode. The engine changed, so the runtimes are
new.
Changed
- Pi 1.6.0: Pi-Bolt's changes are kept on top of it. Extensions that change the lines a component's
render()returns in
place must copy them first: Pi 1.6.0 returns the same cached array while a component is unchanged. - The engine keeps a standalone executable's bytecode and string table once: on macOS and Linux the module graph points
into the compiled heap instead of holding a second copy. Windows keeps its copy in the graph. - The regular screen keeps one snapshot of the transcript and rewrites only the rows that changed. Opening an overlay or
editing below an earlier Kitty image reuses the rows above it. - Fullscreen reuses the formatting of rows that stay in place or move with a scroll, and on exit writes the transcript to
the scrollback in bounded pieces. A resumed session draws the rows in view; earlier rows are drawn when you scroll to them. - Transcript search keeps earlier matches after an edit and searches again only around it, phrases across the edit
included. - Streaming Markdown reuses the rows of a growing paragraph up to the last unchanged word; code blocks and their
highlighting continue from the previous frame. - Tool history: a finished tool row keeps its rendered lines and drops the components that drew them; clicking or resizing
builds them again. - Requests reuse the bytes of messages already sent in the session, including file contents that an edit left unchanged,
and are released when the session closes or is compacted. - Sessions: entries, totals and the tree are served from indexes that appends extend, so RPC
get_entries,
get_session_statsand the session tree's search stay fast on long sessions. A fork is written whole to a temporary file
and then put in place. - Large files:
readpages through a file of 1 MB or more with a sparse index of its lines, andeditapplies its
replacements in one pass. - Saved subagent transcripts send capped previews of very large tool arguments over RPC and remote control without
reading them whole. - Startup profile: recorded for Pi 1.6.0, on macOS and Linux, with the prebuilt heap's order on Windows.
- Two defaults stay as they were. Pi 1.6.0 makes GPT-6.2 Sol the default model of the
openai,azureand
openai-codexproviders; Pi-Bolt keeps GPT-6.1 Sol (GPT-6.2 Sol and Astra can be chosen). Pi 1.6.0 turns Anthropic message
threads on for any provider whose address is on api.anthropic.com; Pi-Bolt keeps them on by default for theanthropic
provider only (compat.supportsMessageThreadsturns them on for another).cacheWarmingstays"streaming", and remote
control stays off until you turn it on.
Added
- Automatic updates, off by default (#319): turn on Automatic
updates in/settings; Pi-Bolt then installs a new release in the background at most once a day. It never compiles
extensions. pi-bolt --herdr-pi(#157): in a Herdr pane,
Pi-Bolt reports as Herdr's own Pi integration, so Herdr stores the session.PIBOLT_VARIANT=jitselects the JIT build of the platform you are on, with the installers and with npm.
PIBOLT_NO_PATH=1installs a build without changing thepi-boltcommand, so the JIT build can sit beside the default one.- Linux x86-64 start helper: the release's
pi-startreads the executable ahead while Pi starts, on a cold page cache.
pi-bolt, the installer and the npm launcher use it when it is there.
Fixed
- A fork stopped while it was being written no longer leaves a temporary file in the session folder.
Measured on macOS on Apple silicon (an M5), 1.2.1 / 1.3.0, medians of 22 runs, builds interleaved:
| Instructions | CPU | Peak memory | |
|---|---|---|---|
pi --version
| 55 / 54 M | 4 / 4 ms | 6 / 6 MB |
pi -p (5 model turns), blank home
| 188 / 169 M | 17 / 15 ms | 20 / 19 MB |
pi -p, typical home
| 206 / 186 M | 18 / 17 ms | 21 / 20 MB |
pi -p, typical home with opensec-pi-subagents and opensec-pi-todo
| 435 / 420 M | 42 / 40 ms | 33 / 32 MB |
| Interactive, 5 prompts | 561 / 434 M | 84 / 78 ms | 27 / 25 MB |
| 60,000-character answer, per frame (10 runs) | 1.26 / 1.24 M | ||
Resuming a 2,292-entry session (pi -c, fullscreen), until the first frame (14 runs)
| 492 / 386 M | 78 / 30 MB |
Peak memory is the physical footprint; for resuming, the footprint once drawing settles. The answer row streams at 1,200
characters a second (bench/long_answer.py). Resuming in fullscreen draws the rows in view; the rest of the transcript is
drawn when it is scrolled to (1.2.1 drew all of it after the first frame: 6,278 / 453 M instructions until drawing settles).
Measured on Linux x86-64 (an AMD EPYC 9355P, shared with other work), 1.2.1 / 1.3.0, medians of 22 runs, builds
interleaved:
| CPU | Peak memory | |
|---|---|---|
pi --version
| 5 / 5 ms | 2 / 2 MB |
pi -p (5 model turns), blank home
| 30 / 29 ms | 17 / 15 MB |
pi -p, typical home
| 32 / 30 ms | 17 / 16 MB |
pi -p, typical home with opensec-pi-subagents and opensec-pi-todo
| 80 / 77 ms | 29 / 28 MB |
| Interactive, 5 prompts | 124 / 106 ms | 26 / 24 MB |
| 60,000-character answer, per frame (10 runs) | 0.95 / 0.91 ms | |
Resuming a 2,292-entry session (pi -c, fullscreen), until the first frame (14 runs)
| 86 / 61 ms | 76 / 26 MB |
Peak memory is the private memory. 1.3.0 started with pi-start.
Largest changes (macOS / Linux, 1.2.1 → 1.3.0, medians):
- A saved subagent edit holding 32 Mi characters reaches an RPC client in 34 / 50 ms instead of 10.5 / 10.6 s, with 41 / 35 MiB
instead of 988 / 1,119 MiB (n=12). - RPC
get_entriesandget_session_statson a 12,000-entry session: 0.008-0.009 ms of CPU per query instead of 0.12-0.32 ms
(n=12). - Session tree search on a branched session (1,024 leaves): 1.4 / 1.3 ms per keystroke instead of 34 / 47 ms (n=12).
- Resuming a 2,292-entry session in fullscreen: 453 M instructions and 35 ms of CPU until drawing settles instead of 6,278 M and
357 ms on macOS; 30 / 26 MB instead of 78 / 76 MB (n=14). - 101 interactive tool prompts: 59 / 59 MiB at the end instead of 95 / 91 MiB, and 8.5% / 16% less CPU per prompt (n=10).
- 6,000 restored messages in RPC: 27% / 32% less CPU per prompt (n=12).
- Interactive, 5 prompts: 23% fewer instructions (561 → 434 M) on macOS; 15% less CPU on Linux (n=22).
Some rows cost a little more. A single answer right after launch takes 0.5 ms more CPU in the TUI on macOS (11.7 → 12.2 ms,
more of it system time, with fewer instructions) and 0.1 to 0.4 ms more over RPC (about 1.2 M more instructions per answer);
later answers in the same process are not slower. On Linux, starting through pi-start costs about 1.2 ms of CPU on a warm
page cache in exchange for the faster first frame. Idle memory on Linux is 0.7 MiB higher (13.9 → 14.6 MiB); idle CPU on Linux
is about half of 1.2.1's. Raw results and the scripts: bench/results/2026-11-22-1.3.0-vs-1.2.1.
Runtimes
Built by the runtime workflow (run 44946110942) from
pi-bolt at 3c29bca79 (runtime stamp 13ef7565ee8ee6b5), each on its platform's runner, tested there (tests/aot,
tests/runtime) and attested; the release workflow checked those attestations and packed the runtimes into the archives below,
which it attests in turn: gh attestation verify <file> -R opensec-git/Pi-Bolt.
| Runtime | SHA-256 |
|---|---|
pi-bolt-runtime-linux-x64.tar.gz
| 88169bd293739905c5a5048e45da66bcc6808b47e6d9f82481e28b89295c82f4
|
pi-bolt-runtime-linux-x64-musl.tar.gz
| 22ef6222e58415c4f4fe9d0b8af47e3715419b785b7ad3ae3a13eabfa2747e1e
|
pi-bolt-runtime-linux-arm64.tar.gz
| 6c9906c974817082fd56fecf792610adba3a2883fd0b391facaa692099032326
|
pi-bolt-runtime-darwin-arm64.tar.gz
| 7701f25ff372aff217b7717bd1de590a7c5ef8e104cb221901842d2cbd207151
|
pi-bolt-runtime-win32-x64.zip
| 21f5ed08df4b523c639cb972827b62f3771a84fc06b3d6b13c1f244202d0d7a8
|
Install
curl -fsSL https://pi-bolt.opensec.in/install.sh | shirm https://pi-bolt.opensec.in/install.ps1 | iexpowershell -c "irm https://pi-bolt.opensec.in/install.ps1 | iex"or pi-bolt update, or npm install -g --allow-scripts=pi-bolt pi-bolt, or bun add -g --trust pi-bolt, or:
- Homebrew (macOS on Apple silicon, Linux):
brew install opensec-git/tap/pi-bolt - Scoop (Windows):
scoop bucket add opensec-git https://github.com/opensec-git/scoop-bucket, thenscoop install opensec-git/pi-bolt - mise:
github:opensec-git/Pi-Boltwith the options in the installation guide
The installer checks the release signature with OpenSSL 3, ssh-keygen (OpenSSH 8.1 or later), or an installed Pi-Bolt.
Every archive also has a GitHub build attestation: gh attestation verify <file> -R opensec-git/Pi-Bolt.
| Asset | For |
|---|---|
pi-bolt-linux-x64.tar.xz / .tar.gz
| Recommended on Linux x86-64. CPUs with AVX2 (Intel Haswell 2013+, AMD Zen+). |
pi-bolt-linux-x64-baseline.tar.xz / .tar.gz
| Any x86-64 CPU with SSE4.2. |
pi-bolt-linux-x64-jit.tar.xz / .tar.gz
| JIT also on, for plugins loaded at run time. |
pi-bolt-linux-x64-musl.tar.xz / .tar.gz
| Alpine Linux and other musl systems on x86-64 (AVX2). Needs libstdc++.
|
pi-bolt-linux-x64-musl-baseline.tar.xz / .tar.gz
| musl on any x86-64 CPU with SSE4.2. |
pi-bolt-linux-x64-musl-jit.tar.xz / .tar.gz
| musl, JIT also on. |
pi-bolt-linux-arm64.tar.xz / .tar.gz
| Linux on ARM64, any 64-bit ARM CPU; Android in Termux, with the installer. |
pi-bolt-linux-arm64-jit.tar.xz / .tar.gz
| Linux on ARM64, JIT also on. |
pi-bolt-darwin-arm64.tar.xz / .tar.gz
| macOS. Macs with Apple silicon, macOS 13 or later. |
pi-bolt-darwin-arm64-jit.tar.xz / .tar.gz
| macOS, JIT also on. |
pi-bolt-win32-x64.zip
| Windows. Windows 10 (1809) or 11 on x64; compiled code on AVX2 CPUs, bytecode on others. |
pi-bolt-win32-x64-jit.zip
| Windows, JIT also on. |
pi-bolt-runtime-linux-x64.tar.gz, pi-bolt-runtime-linux-x64-musl.tar.gz, pi-bolt-runtime-linux-arm64.tar.gz, pi-bolt-runtime-darwin-arm64.tar.gz, pi-bolt-runtime-win32-x64.zip
| The Pi-Bolt Bun runtime, for compiling plugins in. |
pi-bolt-kit-linux-x64.tar.gz, pi-bolt-kit-linux-x64-musl.tar.gz, pi-bolt-kit-linux-arm64.tar.gz, pi-bolt-kit-darwin-arm64.tar.gz
| What pi-bolt compile builds with, besides the runtime.
|
install.sh, install.ps1
| The installers, listed in the signed SHA256SUMS: pi-bolt update runs them only after checking them.
|
Linux x86-64 or ARM64 with glibc 2.17 or later; Alpine and other musl Linux on x86-64; Android 7 or later on 64-bit ARM, in Termux; macOS 13 or later on Apple silicon;
Windows 10 1809 or later, or Windows 11, on x64.