@mariozechner/pi-coding-agent
0.73.1 · 7 May 2026MIT443.1k / weekRepositoryHomepagenpmAtom feed
Upgrading @mariozechner/pi-coding-agent From 0.67.0 to 0.67.1
1 release in betweenevery note read
Reading releases, release notes and advisories…
Security
3 advisories still affect 0.67.1
- Pi Agent: Potential XSS in HTML session exports via Markdown URL sanitization bypasslow · GHSA-7v5m-pr3q-6453
- Pi Agent: Predictable temporary extension install paths allow local privilege escalation on shared Linux hostshigh · GHSA-jfgx-wxx8-mp94
- Pi Agent: Race condition in Pi auth.json writes could expose stored credentialslow · GHSA-r95r-rj6r-c39x
No published version clears them all yet.
Release by release
- New
Full
openRouterRoutingsupport inmodels.json, including fallbacks, parameter requirements, data collection, ZDR, ignore lists, quantizations, provider sorting, max price, and preferred throughput and latency constraints. See docs/models.md. - New
PI_CODING_AGENT=trueenvironment variable set at startup so subprocesses can detect they are running inside the coding agent. - New
Added full
openRouterRoutingfield support inmodels.json, including fallbacks, parameter requirements, data collection, ZDR, ignore lists, quantizations, provider sorting, max price, and preferred throughput and latency constraints - New
Set
PI_CODING_AGENT=trueenvironment variable at startup so sub-processes can detect they are running inside the coding agent
- New
14 other lines we could not sort, mostly version bumps
- 0.67.1
Pi needs a reliable per-version usage signal to understand whether releases are being adopted and to help justify funding continued development.
- 0.67.1
Npm download counts are not a reliable proxy for actual Pi usage.
- 0.67.1
It only runs in interactive mode.
- 0.67.1
It does not run in RPC mode, print mode, JSON mode, or SDK mode.
- 0.67.1
On a fresh interactive install, Pi writes
lastChangelogVersion, then sends the ping. - 0.67.1
On later interactive startups, if the local changelog contains entries newer than the previously stored
lastChangelogVersion, Pi writes the newlastChangelogVersion, then sends the ping. - 0.67.1
The request is fire-and-forget. Startup does not wait for it, and any errors are ignored.
- 0.67.1
Only the Pi version in the request path, for example
https://pi.dev/install?version=0.67.1. - 0.67.1
The server stores only aggregate per-version counters such as
{ "0.67.1": 3 }. - 0.67.1
It does not store IP addresses, client identifiers, prompts, paths, models, auth state, or any other per-user data. It literally only increments a counter for that version.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.