xz-dev/pi

This is a downstream distribution fork of earendil-works/pi.

It tracks upstream main with a minimal downstream patch stack.

Warning

This fork relies heavily on vibe coding. Logic changes are manually reviewed, and tests are also written by AI under human direction before the full test gate is run.

Almost none of the code in this fork is handwritten by xz-dev. Do not use this distribution if you are uncomfortable with AI-assisted development.

Downstream changes

Features

• Continue from the nearest protocol-safe conversation boundary with /retry or RPC retry, preserving superseded history as an append-only sibling branch, retaining completed tool results, and synthesizing explicit unknown-outcome errors only for missing results without replaying old tool calls.
  • Patch branch: patch/manual-retry
• Support per-package Skill visibility overrides through skillOverrides.<name>.disableModelInvocation, retaining manual /skill:<name> invocation and project-over-global precedence.
  • Patch branch: patch/skill-overrides
• Allow settings.retry.nonRetryableErrorPatterns to fail-fast on gateway-specific terminal quota/limit error messages without expanding the built-in retry classifier.
  • Patch branch: patch/retry-non-retryable-patterns

Fixes

• earendil-works/pi#6234: make Esc abort recover from lifecycle hooks, extension hooks, provider setup, provider streams, or listener dispatch that never settle.
  • Patch branch: patch/esc-abort

The integrated Esc and manual-retry patches both extend the Agent failure lifecycle. Their independent branches remain directly reviewable; tmp/patch/esc-manual-retry-compat supplies only the downstream combined handleRunFailure() resolution and is merged immediately after them.

Temporarily disabled

These branches still exist but are not squash-merged into rebuilt main until they are rebased onto current upstream:

• Provider catalog refresh consistency
  • Patch branch: patch/model-refresh-consistency
• TUI synchronized-output hardware cursor positioning
  • Patch branch: patch/tui-synchronized-cursor

Maintenance

• Keep the fork/pre-release changelog baseline, display, and version handling correct across downstream release cycles.
  • Patch branch: patch/changelog-prerelease

Unsupported

• Provider-transparent compaction keeps one portable session history across providers while allowing compatible providers to resume from private checkpoints. This feature is retired and explicitly unsupported.
  • Archived branch: retired/provider-transparent-compaction
  • Responses API compaction does not reduce API charges: compacted or provider-held context remains billable. It also makes the client-visible state machine opaque, and that hidden state can amplify charges in some cases through unexpected context retention, replay, or repeated compaction.

Installation

GitHub Packages requires authentication for npm installs, including public packages. Create a GitHub classic token with read:packages, then log in:

npm login --scope=@xz-dev --auth-type=legacy --registry=https://npm.pkg.github.com

Install from GitHub Packages:

npm config set @xz-dev:registry https://npm.pkg.github.com
npm install -g @xz-dev/pi-coding-agent
pi --version

Note

npm 12 disables remote tarball dependencies by default. This distribution uses GitHub Packages tarball URLs for its workspace packages, so installation or pi update may fail with EALLOWREMOTE and Fetching packages of type "remote" have been disabled. Enable them for your user configuration, then retry:

npm config set allow-remote=all --location=user
pi update
pi update --extensions

Automation upstream sync

See MAINTAIN.md for the authoritative downstream branch ownership, rebuild, publication, recovery, and patch-retirement rules.

Twice daily, Upstream Sync rebuilds main from the latest https://github.com/earendil-works/pi.git main, then integrates the maintenance overlay, feature and fix branches, and temporary compatibility branches in a fixed order:

• 01:28 Asia/Shanghai
• 13:28 Asia/Shanghai

Before a lease-protected update of main, the workflow installs dependencies, hydrates model data, builds, checks, runs focused integration regressions, audits production and development dependencies, and verifies production dependency signatures. Conflicts, empty integrations, failed gates, or a changed remote lease leave main unchanged. A successful push triggers the full CI, Esc Abort Integration, and Publish GitHub Packages workflows for the rebuilt commit.