@eforge-build/pi-eforge

Pi package for eforge.

Install in Pi:

pi install npm:@eforge-build/pi-eforge

Or install for the current project only:

pi install -l npm:@eforge-build/pi-eforge

Then, in your project:

/eforge:init

What this package provides

• Native Pi tools for eforge daemon operations, including eforge_extension and eforge_extension_contribution with compact default projections, bounded shared Markdown/JSON formatting, summarized failed-invocation envelopes, and a 12,000-character host-output budget for coding-agent tool text
• Native Pi commands for agent runtime profile management (/eforge:profile, /eforge:profile:new), config viewing (/eforge:config), status dashboards (/eforge:status), safe daemon restarts (/eforge:restart), build source review (/eforge:build), and extension contribution browsing (/eforge:extensions list/show/invoke without dumping raw manifests by default) with interactive TUI panels and selectors
• Compact Pi host output is the default for extension management and contribution tools. Contribution lists preserve whole entries and report returned/total/next-offset continuation within the 12,000-character budget; use CLI --json or typed daemon/client HTTP APIs for intentional raw/debug inspection.
• Slash commands for build operations (/eforge:build, /eforge:init, /eforge:update)
• Generic contribution discovery/detail/invocation and workstation routing; when the eforge-plan extension is loaded/trusted, these can surface its planning entry, workstation deep link (for example /console/workstations/eforge-plan%3Aplanning-workstation), and SQLite store/search/maintenance actions through the same generic contribution surface
• The /eforge:extend skill for assisted eforge TypeScript extension authoring
• Generic extension-provided workflows are discovered and invoked through /eforge:extensions and the eforge_extension_contribution tool
• The /eforge:recover skill for reviewing and acting on failed-PRD recovery verdicts
• The /eforge:stack:sync skill and eforge_stack_sync tool for manually synchronizing the git-spice stack, previewing with --dry-run, interpreting sync reports (including deferred outcomes and retry-deferred triggers when active builds overlap the stack), and recovering from manual sync conflicts (requires git-spice installed and git-spice repo init run in the repository)
• The /eforge:workflow skill for configuring the eforge workflow preset (landing action, stacking, PR settings, and daemon-owned after-build sync via stacking.sync.afterBuild) through a native Pi select-overlay wizard, including /eforge:workflow:init (initial setup) and /eforge:workflow:reconfigure (change the active preset)
• Ambient status display showing active profile, queue count, and build progress (passive — does not start the daemon)
• Orchestrator decision events (plan:build:decision) flow through the daemon event stream unchanged. Rich live rendering (timeline track, decision detail, and build activity) lives in Console.

Requirements

• Node.js 22+
• Pi
• An LLM provider credential supported by your chosen eforge harness

Relationship to the @eforge-build/eforge npm package

@eforge-build/pi-eforge is the Pi integration package.

The main @eforge-build/eforge npm package is the standalone CLI and daemon runtime that this Pi package invokes via npx -y @eforge-build/eforge.

For project docs and full setup guidance, see the main repository:

• GitHub: https://github.com/eforge-build/eforge
• Docs: https://eforge.build