opensec-git / Pi-Bolt

Pi-Bolt 
 The 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. 
Pi-Bolt is the Pi you already use, with the same commands, sessions, settings, providers and extensions. Every function is
compiled to machine code when the executable is built, so nothing is parsed or JIT-compiled at launch. It is ready to type 2.4
times sooner than Pi on Bun and uses 2.7 times less CPU over a session; against Pi on Node, 9 times sooner, 6 times less CPU,
11 times less for a long answer and a third of the memory.
 GitHub's Linux x86-64 runner, one CPU each. Pi-Bolt against the same Pi on stock Bun and on Node 22 and 24; the long answer
is 60,000 characters; lower is better. See Benchmarks, also against PiG. 
> [!NOTE]
> Pi-Bolt is an independent fork of Pi, not affiliated with Pi's authors or with Oven.
## Install
 [code] 
The same command installs Pi-Bolt on Linux x86-64 and ARM64, on macOS, and on Android in Termux. On Arch Linux there is also
a community package in the AUR, `pi-bolt-avx2-bin-release-git`
(the x86-64 AVX2 build, signature checked): `paru -S pi-bolt-avx2-bin-release-git`.
On Windows, in PowerShell:
 [code] 
or in Command Prompt:
 [code] 
or `npm install -g --allow-scripts=pi-bolt pi-bolt`, or `bun add -g --trust pi-bolt`. Then run `pi-bolt` in your project. Your
Pi configuration in `~/.pi/agent` is used as is; new to Pi? Run `/login` to connect a provider. `pi-bolt update` installs the
latest release, `pi-bolt update --rollback` puts back the build it replaced, and `pi-bolt update --channel beta` takes
pre-releases too.
The installer verifies the release signature and offers three optional extensions by OpenSec:
| Extension | What it does |
|---|---|
| `opensec-pi-subagents` | Specialized agents in separate sessions, parallel workflows and scheduled jobs |
| `opensec-pi-todo` | A todo list for the model, shown as a live panel above the editor |
| `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.
 [code] 
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, check it against
`