opensec-git/Pi-Bolt bolt-v1.1.3

Pi-Bolt 1.1.3

on GitHub

Pi-Bolt 1.1.3 is 1.1.2 with /remote-control reaching the phone from anywhere by default. Pi is still 1.5.0,
and the engine and runtimes are 1.1.1's.

Changed

• /remote-control starts the Cloudflare tunnel by default (#251):
  when cloudflared is installed, plain /remote-control starts the tunnel (a quick tunnel, or the named one in
  remoteControl.tunnel) together with the LAN listener, so the phone connects on the same network or from anywhere. If the
  tunnel fails, the LAN keeps working and a warning is shown; /remote-control tunnel still treats a tunnel failure as an
  error. The first time cloudflared is missing, Pi offers to install it (brew on macOS, winget on Windows, run only
  if you choose it; on Linux it shows the download page), to stay on the LAN for now, or not to ask again
  (remoteControl.askCloudflared: false). /remote-control lan is local only and stops a running tunnel;
  remoteControl.tunnel: "off" makes that the default. Tailscale addresses in the pairing code are labelled tailscale.
  Nothing of it loads until the command runs.

Also since 1.1.2, outside the release archives:

• pi-bolt.opensec.in/android: download the Android app
  (#245).
• Android app 0.2.1: OpenSec's subagents and todo extensions in the on-device engine
  (#248), released on its own under android-v tags.
• The Android app's on-device engine moves to Pi-Bolt 1.1.2 (#250).
• Android app 0.2.2: in-app updates from GitHub releases (#252).

With the default settings Pi-Bolt sends what Pi 1.5.0 sends. The release archives on the Apple M5, 1.1.2 / 1.1.3
(medians of 25 runs, 50 for pi --version and interactive; a second copy of 1.1.2 varied as much). Android builds were
running on the Mac (load average 30-50), so the times are higher than on an idle Mac: compare the two columns, not the tables
of earlier releases.

The second copy of 1.1.2 measured 63 M / 26.6 ms, 218 M / 78.7 ms and 680 M / 234 ms for the first three rows. The TUI is
ready for input after 68.8 / 66.3 ms (-jit 60.7 / 57.0 ms). The executable is 66 KB larger than 1.1.2's and peak
memory is unchanged; the remote-control code still loads only when /remote-control runs. Waiting at the prompt (0.54 /
0.51 ms of CPU per second) and streaming a 60,000-character answer (2.68 / 2.35 s of CPU, 40 / 36 MB) cost the
same as in 1.1.2.

Install

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

irm https://pi-bolt.opensec.in/install.ps1 | iex

powershell -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, then scoop install opensec-git/pi-bolt
• mise: github:opensec-git/Pi-Bolt with 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.

Linux x86-64 or ARM64 with glibc 2.17 or later; 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.