Pi Milestones

Branch-aware, user-controlled milestones for the Pi coding agent.

Behavior

• The user creates, edits, deletes, completes, and controls Pi’s ongoing completion permission.
• Pi reads active milestones from hidden per-turn context.
• Pi can list or change milestones when directly requested in the current user message.
• Milestones with ongoing Pi completion permission can be completed without a new request.
• Milestone state follows the active Pi conversation branch.
• A widget, inline event cards, /milestones, and /tree labels display milestone state.

Pi actions require an explicit request in the current user message, except when Pi already has ongoing completion permission. The extension does not verify completion criteria.

Installation

Install the package globally for Pi:

pi install npm:pi-milestones

Try it for one session without installing:

pi --no-extensions -e npm:pi-milestones

Review third-party Pi packages before installation. Extensions run with full system access.

Development

Requirements: Node.js 22.19 or newer. Tested with Pi 0.84.2.

npm install
npm run verify
pi --no-extensions -e ./src/index.ts

After changing the extension, run /reload inside Pi.

Commands

/milestone-add [title]
/milestone-edit [id] [title]
/milestone-complete [id]
/milestone-delegate [id]
/milestone-revoke [id]
/milestone-delete [id]
/milestones

Omit an ID in interactive mode to select an eligible milestone from a list.

The agent receives one tool:

manage_milestones(action, id?, title?, userRequest?)

Actions: list, add, edit, complete, allow_completion, require_request, and delete.

userRequest is an exact excerpt from the current user message and grants one-turn permission. It is omitted only when Pi already has ongoing completion permission.

Display

• ○ active and controlled by the user
• ◇ active and Pi can mark it complete without a new request
• ✓ completed

The compact widget appears above the editor. Milestone changes render as durable chat entries. Completion points receive labels such as milestone-3-completed in /tree.

Scope

Milestones are stored in Pi session entries. They are not shared across sessions or projects and do not use external storage.

The authorization model is an extension capability rule, not a security sandbox against unrestricted filesystem tools.