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-10-24-pi-coding-agent-exact-internal-package-versions-and-the-nix-repairs-have-shipped

Exact internal package versions and the Nix repairs have shipped. Fresh npm installs no longer resolve incompatible versions of Pi’s own packages through permissive internal ranges. Nix no longer expects removed chord/esbuild dependencies, refreshes an incompatible model-catalog pin before release, and puts its Node on PATH as a fallback instead of overriding the operator’s shell Node. These are shipped answers to the previous harvest’s main-only leads. At the UTC reads in Install today, GitHub newest stable, npm latest, the managed installer selector and Nix stable all select 1.4.0; Node >=22.19.0 is required for the documented install route. Nix stable points to the successfully built 1.4.0 tag.

Channel: tagged-release. Half: both. Date: 2026-10-15.

Operator consequence: Move a reproducible deployment to 1.4.0 and record the actual dependency graph. The Nix availability blocker is resolved, and shell tools can use the operator’s Node again. Keep the distinction between exact internal versions and a fully locked installation: the former removes one source of drift, not all of them. Human attention can move from reconstructing mixed Pi versions to testing extensions and provider behavior.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-pi-coding-agent-exact-internal-package-versions-and-the-nix-repairs-have-shipped

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact