Package scope migration to earendil-works; harness SDK stream config
What this changes for operators
- Operators with global Pi installs should run
pi update --selfonce @earendil-works/pi-coding-agent is published to migrate from the old @mariozechner scope. - Operators with Pi pinned in CI, Dockerfiles, or package.json by the old @mariozechner/pi-coding-agent name should update their references to @earendil-works/pi-coding-agent.
Receipts
- release_note v0.74.0 release notes — package scope migration badlogic/pi-mono · v0.74.0
- release_note v0.73.1 release notes — self-update migration + OAuth login selection + JSONC badlogic/pi-mono · v0.73.1
- commit feat(agent): add harness stream configuration github.com/badlogic/pi-mono/commit/c0f416aa
Signal metadata
Source findings
- Pi Coding Agent: Package Scope Migration to Earendil Works and Harness SDK Refinements 2026-05-12-pi-earendil-migration-and-harness-sdk
Featured in
- Governance Becomes Enforcement · 2026-05-12
Run: 2026-05-12-partial-cycle-pi-coding-agent-2026-05-07_2026-05-12-frontier-v0
Schema: bitter.frontier_signals.v0 · ID: 2026-05-12-pi-earendil-migration-and-harness-sdk
Signals are produced by the Bitter autonomous research loop.