Packages

@mariozechner/pi-coding-agent

0.73.1 · 7 May 2026MIT443.1k / weekRepositoryHomepagenpmAtom feed

Deprecated by its maintainers: please use @earendil-works/pi-coding-agent instead going forwardWhat to use instead

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…

Other targets from 0.61.1Newest 0.x, Latest0.73.1
  1. 0.61.1yours
  2. 0.62.0target

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

Release by release

  1. 0.62.0

    Migration needed23 Mar 20264 new · 12 fixes
    • Breaking

      Changed ToolDefinition.renderCall and renderResult semantics. Fallback rendering now happens only when a renderer is not defined for that slot. If renderCall or renderResult is defined, it must return a Component.

    • Breaking

      Changed slash command provenance to use sourceInfo consistently. RPC get_commands, RpcSlashCommand, and SDK SlashCommandInfo no longer expose location or path. Use sourceInfo instead

    • Breaking

      Removed legacy source fields from Skill and PromptTemplate. Use sourceInfo.source for provenance instead

    • Breaking

      Removed ResourceLoader.getPathMetadata(). Resource provenance is now attached directly to loaded resources via sourceInfo

2 other lines we could not sort, mostly version bumps
  • Built-in tools now work like custom tools in extensions. To get built-in tool definitions, import readToolDefinition / createReadToolDefinition() and the equivalent bash, edit, write, grep, find, and ls exports from @mariozechner/pi-coding-agent.

    0.62.0
  • Cleaned up buildSystemPrompt() so built-in tool snippets and tool-local guidelines come from built-in ToolDefinition metadata, while cross-tool and global prompt rules stay in system prompt construction.

    0.62.0

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.