Skip to content

Pi-Bolt 0.7.0

Choose a tag to compare

@Kushalkhemka Kushalkhemka released this 05 Oct 16:10

Pi-Bolt 0.7.0 runs Pi 1.0.3, up from 1.0.0, and fixes a crash on macOS when Pi-Bolt is started right after it is installed.

Pi 1.0.3

Everything in Pi 1.0.1, 1.0.2 and 1.0.3, among it:

  • The Azure provider is renamed from azure-openai-responses to azure, and also serves Azure Foundry Chat Completions deployments. Rename the provider in auth.json (or /login again), models.json and settings.json. The AZURE_OPENAI_* variables are unchanged.
  • samplingParamsByThinkingLevel in models.json: sampling parameters, such as temperature, for each thinking level.
  • Project overrides for MCP servers in .pi/mcp.json and /mcp, and MCP sign-in with a Client ID Metadata Document.
  • pi.registerToolRenderer() for extensions, which draws calls to tools that are not registered yet.
  • Home and End always move the editor's cursor; the fullscreen transcript's top and bottom are Ctrl+Home and Ctrl+End.
  • Fixes for subscription sign-ins after a cancelled request, codemode output that ran out of memory, images in Kitty, Ghostty, WezTerm and Warp, and providers' "at capacity" errors, which are now retried.

Pi-Bolt's own changes are kept: messages name the pi-bolt command, and pi-bolt update updates Pi-Bolt.

macOS

  • Pi-Bolt starts when it is given the terminal as /dev/tty. Answering "Start pi-bolt now?" with Y at the end of the installer stopped with EINVAL from kqueue. The installer of 0.6.1 had worked around it since; now Pi-Bolt reads keys from a terminal opened that way.

Installer

  • A release without a valid signature is not installed. From 0.6.0 on, a missing signature now stops the install, as one that does not verify always did, wherever the files come from (PIBOLT_DOWNLOAD_BASE included). The signature is checked with OpenSSL 3, on PATH or Homebrew's, or else with the Pi-Bolt already installed, so pi-bolt update checks it on a Mac without OpenSSL 3 too. A first install with neither checks the checksums, and says so.
  • PIBOLT_BIN_DIR is quoted in the line the installer adds to the shell's configuration.
  • Downloads no longer stall for over a minute. When one of GitHub's addresses did not answer, curl waited for the system's connect timeout (75 seconds on macOS) while the installer said "verifying checksum". Connections now give up after 8 seconds and go to the next address, and the signature is fetched while the release downloads.
  • The npm package carries the same installer.

For builders

  • scripts/fetch-runtime.sh requires the release's signature, checked with OpenSSL 3 or Bun.
  • The engine changes are one patch each: patches/webkit.patch and patches/bun.patch, in place of 41 patches. The source they make is the same.

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.