Skip to content

Pi-Bolt 0.6.1 (Pi 1.0.0)

Choose a tag to compare

@Kushalkhemka Kushalkhemka released this 04 Oct 16:43

Pi-Bolt 0.6.1 changes how the programs Pi starts on macOS are started. It runs Pi 1.0.0. On Linux nothing changes.

macOS

  • The commands, servers and editors Pi starts are started by a helper. Commands of the bash tool, MCP and language servers, a dev server started from Pi: a helper started with Pi now starts them, through pi-spawn, a new file beside pi-bin (ARCHITECTURE.md).
    • A program gets what it got before: its files, directory, environment, signals, limits, and Pi's process group (so it can use the terminal), or a session of its own.
    • child.pid is the program's own pid, and signals go to it.
    • Pi waits for pi-spawn, which exits as the program did.
    • Not covered: programs started on a pseudo-terminal (Bun's terminal option), and Pi's executable started directly, without the pi launcher. Those programs are started directly, as before.
  • What it costs:
    • 0.3 ms more at each start (not for pi --version);
    • 1.4 ms more for each program Pi starts.

All platforms

  • Messages name the pi-bolt command. pi-bolt --help, the hints after a failed extension load, the resume command printed on exit, pi-bolt auth and pi-bolt mcp said pi, which is not what the installer and npm install. Pi's environment variables and files keep their names.
  • The installer offers OpenSec's two extensions, opensec-pi-subagents and opensec-pi-todo, new on npm under the Apache License 2.0.
    • These are Bun builds that load in Pi-Bolt without being transpiled.
    • It asks first. It does not offer one that is installed already, or when another extension of the same kind is (any subagents or todo extension, a local checkout included): Pi would refuse to load both.
    • PIBOLT_EXTENSIONS=yes or no answers in advance. A run that cannot ask installs none.
    • Pi-Bolt installs them itself: with npm where it is installed, otherwise with its own package manager. No Node.js or Bun is needed.
  • The README and the npm README put the standard builds first; the -jit builds are for heavy use of plugins loaded at run time.

Tested

  • A new test starts programs from an extension. It checks:
    • exit codes and signals;
    • ENOENT and EACCES;
    • stdin, stdout, stderr and a fourth descriptor;
    • the working directory and the environment;
    • the pid, kill() and timeouts;
    • the process group;
    • a detached shell killed with its children as a group, as Pi's bash tool does.
  • An editor started with Ctrl+G reads the terminal.
  • The installer on macOS and on Debian 12 (amd64) with nothing but curl: no npm, Node.js, Bun or xz.
    • It installs both extensions with Pi-Bolt's own package manager.
    • It asks, and installs on Enter; it skips installed packages and their upstream versions.
    • The extensions' tools run against a local model.
  • An extension from npm that is not OpenSec's (@juicesharp/rpiv-todo), with its dependency, installed and run without npm.

Install

curl -fsSL https://pi-bolt.opensec.in/install.sh | sh

or pi-bolt update, or npm install -g pi-bolt. The installer detects Linux or macOS by itself.

Asset For
pi-bolt-linux-x64.tar.xz / .tar.gz Recommended on Linux. 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-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-runtime-linux-x64.tar.gz, pi-bolt-runtime-darwin-arm64.tar.gz The Pi-Bolt Bun runtime, for compiling plugins in.

Linux x86-64 with glibc 2.17 or later; macOS 13 or later on Apple silicon.