Evidence record / pi-coding-agent
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-08-10-pi-coding-agent-bun-standalone-binaries-crashed-at-startup-in-any-directory-containing
Bun standalone binaries crashed at startup in any directory containing a bunfig.toml with preload.
Pi's compiled Bun standalone binaries crashed on startup whenever the current working directory contained a bunfig.toml declaring preload. The binary was autoloading the project's bunfig and executing its preload scripts inside itself. Fixed by compiling with --no-compile-autoload-bunfig. Contributed by @geril07.
Channel: tagged-release. Ancestry: Listed under Fixed in the v0.84.1 release body, referencing PR #7685. Backing commit beeca6ab ("fix(coding-agent): disable bunfig autoload in compiled binaries (#7685)", 2026-08-06T15:16:12Z) appears in the commit range returned by gh api repos/earendil-works/pi/compare/v0.83.0...v0.84.2, between the v0.84.0 and v0.84.1 tag points. v0.84.1: prerelease=false, published 2026-08-07T06:07:00Z.
Operator consequence: Upgrade if you install Pi as a standalone binary and work on Bun projects. Before 0.84.1 the failure looked like Pi being broken rather than the directory being the trigger, which is a hard symptom to diagnose. Worth noting for its own sake: a compiled agent binary was reading and running a preload script out of whatever directory it happened to be started in.
Receipt
Finding metadata
Run: 2026-08-10-weekly-digest-2026-08-03_2026-08-10-frontier-v0
Finding ID: 2026-08-10-pi-coding-agent-bun-standalone-binaries-crashed-at-startup-in-any-directory-containing
Source links
Primary links, including exact changelog lines when available.
Versioned source: run artifact