@mariozechner/pi-coding-agent
0.73.1 · 7 May 2026MIT443.1k / weekRepositoryHomepagenpmAtom feed
Upgrading @mariozechner/pi-coding-agent From 0.61.1 to 0.62.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 14
- changes to make
- 0
- advisories fixed
- 4
- new
- 12
- fixes
Before you upgrade
Tick each one off as you go- Breaking0.62.0
- Breaking0.62.0
- Breaking0.62.0
- Breaking0.62.0
- Breaking0.62.0
- Breaking0.62.0
- Breaking0.62.0
- Breaking0.62.0
- Breaking0.62.0
- Breaking0.62.0
Security
3 advisories still affect 0.62.0
- 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
- Breaking
Changed
ToolDefinition.renderCallandrenderResultsemantics. Fallback rendering now happens only when a renderer is not defined for that slot. IfrenderCallorrenderResultis defined, it must return aComponent. - Breaking
Changed slash command provenance to use
sourceInfoconsistently. RPCget_commands,RpcSlashCommand, and SDKSlashCommandInfono longer exposelocationorpath. UsesourceInfoinstead - Breaking
Removed legacy
sourcefields fromSkillandPromptTemplate. UsesourceInfo.sourcefor provenance instead - Breaking
Removed
ResourceLoader.getPathMetadata(). Resource provenance is now attached directly to loaded resources viasourceInfo
- Breaking
2 other lines we could not sort, mostly version bumps
- 0.62.0
Built-in tools now work like custom tools in extensions. To get built-in tool definitions, import
readToolDefinition/createReadToolDefinition()and the equivalentbash,edit,write,grep,find, andlsexports from@mariozechner/pi-coding-agent. - 0.62.0
Cleaned up
buildSystemPrompt()so built-in tool snippets and tool-local guidelines come from built-inToolDefinitionmetadata, while cross-tool and global prompt rules stay in system prompt construction.
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.