Sixteen Pi Coding Agent extensions in one npm workspace. Install only what you need; each package publishes and installs on its own under the @estebanforge scope.
Cross-session memory via the agentmemory REST API.
pi install npm:@estebanforge/pi-agentmemoryBridge Pi to Google Antigravity: ACP driver, approval gates, ask tool.
pi install npm:@estebanforge/pi-antigravity-bridgeAsana tasks, projects, and comments.
pi install npm:@estebanforge/pi-asana-meOne-shot delegation to Antigravity.
pi install npm:@estebanforge/pi-ask-antigravityOne-shot delegation to Claude Code.
pi install npm:@estebanforge/pi-ask-claudeOne-shot delegation to OpenAI Codex.
pi install npm:@estebanforge/pi-ask-codexCodeGraph code intelligence tools.
pi install npm:@estebanforge/pi-codegraph-enhancedDeepWiki repository research.
pi install npm:@estebanforge/pi-deepwikigit + GitHub write policy tools.
pi install npm:@estebanforge/pi-git-meZ.ai GLM provider tuning.
pi install npm:@estebanforge/pi-glm-tweaksRender images inline in the TUI (reads, browser screenshots) without spending model tokens.
pi install npm:@estebanforge/pi-image-inlineHostname indicator.
pi install npm:@estebanforge/pi-hostnameSecond-opinion reference models over transcripts.
pi install npm:@estebanforge/pi-mixture-of-agentsRTK command rewriting and tool output compaction.
pi install npm:@estebanforge/pi-rtk-optimizerReading-diff tool: reduces a git diff to the lines that carry the change.
pi install npm:@estebanforge/pi-show-me-the-meatSlack read and post tools.
pi install npm:@estebanforge/pi-slack-mePer-session token cost ledger.
pi install npm:@estebanforge/pi-token-cost-ledgerOpenCode-style tool rendering for Pi.
pi install npm:@estebanforge/pi-tool-displayAdversarial peer review for Pi: /peer-review diff-reviews every change since the last check (git or plain folders) and passes BLOCKER/RISK findings to the model as untrusted claims; the failure-loop unblock gate (/unblock, /advice) and a pre-publish review boundary ship in the same package.
pi install npm:@estebanforge/pi-peer-reviewZendesk ticket tools.
pi install npm:@estebanforge/pi-zendesk-menpm install # once, at the root
npm run check # typecheck + tests for the whole fleetLayout: each package is uniform. extensions/ holds the pi entrypoint declared in each manifest's pi.extensions field, lib/ holds shared helpers where present, tests/ holds every test. One root tsconfig.json, one root vitest.config.ts, toolchain dependencies live only at the root.
Versions are per-package: a package's version moves only when that package releases. One-off fixes and tweaks release a single package. The fleet stamp exists for moments when everything moves at once (dependency bumps, mass changes): it adds one version level to every package from its own current version, so histories stay independent.
npm run rel <name> patch # release one package: check, bump, lockfile, commit, tag <name>-v<version>
npm run pub <name> # full check, then npm publish for that package only
npm run release:patch # fleet stamp: changelog gate, then +1 on every package, one commit, one tag per packageThe registry holds different versions per package by design. Publish one package at a time with npm run pub <name>; it runs the release gates (changelog stamp, dependency floors) before anything reaches npm. Existing installs keep working: package names and entrypoints are unchanged by the monorepo migration.
MIT.