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-main-continues-startup-when-a-configured-package-cannot-install
Main continues startup when a configured package cannot install. Package installation failures during resource resolution become warnings: startup skips the failed package’s resources and keeps running. The next startup or reload retries. Explicit install and extension-update commands still fail nonzero. This behavior is not in npm latest 1.4.0.
Channel: main-unreleased. Half: both. Date: 2026-10-23.
Operator consequence: Source-based hosts can keep working through a package outage, but must confirm required policy extensions loaded before admitting work. A running process no longer proves that every configured package is present. That policy consequence is inferred from skipped resources, not a demonstrated bypass of a named extension.
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-main-continues-startup-when-a-configured-package-cannot-install
Profile citations
- Pi Coding Agent / claim / pending-package-install-warning
- Pi Coding Agent / posture / governance
Source links
Primary links, including exact changelog lines when available.
Versioned source: run artifact