Prepared for minor release 0.50.0Public

Agent

Model

Claude Opus 4.5 (latest)

Started

Jan 26, 3:52 PM

Messages68

Downloads0

Summary

In Progress

Understand
Oriented user to monorepo packages.
Understand
Verify
Checked current version and changelogs.
Verify
Understand
Verified path handling in code and docs.
Understand

how we going?

Hey! All good here. Let me get oriented.

This is the pi monorepo with packages for:

ai - Unified multi-provider LLM API
agent - Agent runtime with tool calling
coding-agent - The interactive CLI (the main product)
mom - Slack bot delegating to pi
tui - Terminal UI library
web-ui - Web components for chat interfaces
pods - vLLM deployment management

What would you like to work on?

ok, let's do a new minor release 0.50.0

Let me check the current version and the state of the CHANGELOGs across packages.

Current version is 0.49.3. The CHANGELOGs have content in [Unreleased] for:

ai: API registry refactor, Azure OpenAI Responses, OpenRouter routing, proxy support, several fixes
coding-agent: Major release with packages system, hot reload, custom providers, SDK changes, many fixes
tui: Scrollback fix, overlay centering, editor fixes, image ID cleanup

The agent, mom, and web-ui packages have empty [Unreleased] sections (no changes since 0.49.3). Pods doesn't have a CHANGELOG.

Running the minor release:

There's an uncommitted file blocking the release:

This is an untracked file in .pi/extensions/. Should I remove it or add it to .gitignore? (It looks like a local development/testing file.)

ah commit that, just a helper for me during development of coding anget

Now running the release:

Done! Released v0.50.0 to npm:

Package	Status
@mariozechner/pi-ai	✓ published
@mariozechner/pi-agent-core	✓ published
@mariozechner/pi-coding-agent	✓ published
@mariozechner/pi-mom	✓ published
@mariozechner/pi	✓ published
@mariozechner/pi-tui	✓ published
@mariozechner/pi-web-ui	✓ published

Tag v0.50.0 pushed to GitHub. CHANGELOGs updated with new [Unreleased] sections for the next cycle.

+path and -path are exact paths relative to the package root.

Omit a key to load all of that type. Use [] to load none of that type. !pattern excludes matches. +path force-includes an exact path. -path force-excludes an exact path. Filters layer on top of the manifest. They narrow down what is already allowed.

from @packages/coding-agent/docs/packages.md are they really relative to the package root? check other .md files as well, possibly @packages/coding-agent/docs/settings.md for such things

Let me check the implementation to verify what paths are actually relative to:

The documentation is accurate. Looking at the code:

Package filters (object form in packages array):
- applyPatterns(allFiles, userPatterns, packageRoot) at line 1137
- Paths are relative to the package root ✓
Top-level settings arrays (extensions, skills, prompts, themes):
- applyPatterns(allFiles, patterns, baseDir) at line 1231 where baseDir is the settings directory
- Paths are relative to ~/.pi/agent or .pi depending on which settings.json

Both docs are correct for their respective contexts:

packages.md: Describes package filter paths → relative to package root ✓
settings.md: Describes top-level resource arrays → relative to settings file location ✓

The docs are consistent. Was there a specific case you were seeing that seemed wrong?