Extensions for the pi coding agent, published as individual npm packages. Install only what you want.
The native API migration targets Pi 0.99.1+. Upgrade Pi and restart before
loading the new tool-package versions; /reload alone does not update the host.
See the package-by-package native API audit for what changed,
what intentionally stayed custom, and the supported tool-result contracts.
Every package that registers tools ships the skills the model needs to use them correctly — a tool without teaching the model when to reach for it is only half done. UI-only and library-only packages (no tools) do not need skills.
| Package | Downloads | Tools | What it adds |
|---|---|---|---|
@parke.dev/pi-steel |
9 | Steel browser: scrape, search, screenshot, PDF, plus a persistent session for logins and multi-step flows | |
@parke.dev/pi-firecrawl |
4 | Firecrawl scrape, search, map, crawl | |
@parke.dev/pi-background-terminals |
4 | Long-running commands: dev servers, watchers, builds, with a /ps UI |
|
@parke.dev/pi-sentinel |
6 | Criteria-gated wakeups for CI, reviews, deployments, timers, and other external state | |
@parke.dev/pi-subagent |
2 | Production-grade isolated child agents, worktrees, budgets, retries, and the subagent execution SDK used by pi-workflows | |
@parke.dev/pi-workflows |
1 | Multi-phase multi-agent orchestration from a JavaScript program you write | |
@parke.dev/pi-file-search |
2 | First-class fd and rg tools |
|
@parke.dev/pi-file-links |
— | Clickable local file paths in normal user and assistant Markdown | |
@parke.dev/pi-ask-user |
1 | Let the agent ask a multiple-choice question instead of guessing | |
@parke.dev/pi-gauntlet |
1 | Goal + gauntlet loop: named shell checks that must all pass before the agent stops iterating | |
@parke.dev/pi-dispatch |
— | Session-level notification queue: one batched delivery path for sentinel events, subagent completions, and escalations | |
@parke.dev/pi-error-log |
1 | Every tool error captured to one reviewable JSONL log with sanitized args, plus an error_log query tool |
|
@parke.dev/pi-graphiti |
3 | Shared Graphiti memory: recall, remember, and health-check tools backed by a Graphiti MCP server | |
@parke.dev/pi-ext-config |
— | Shared typed config loader used by the packages above | |
@parke.dev/pi-integration-auth |
— | Shared credential resolution, /…-login helpers, and integration-auth.json storage used by the GitHub/Slack/Linear/Notion providers |
|
@parke.dev/pi-integration-http |
— | Shared bounded-retry HTTP client used by the integration providers | |
@parke.dev/pi-herdr |
3 | Dispatch, monitor, and safely clean up pi agents in herdr-managed worktrees, with PR-review dispatch and trust | |
@parke.dev/pi-git |
5 | Structured Git status, diffs, branches, history, and pre-PR checks | |
@parke.dev/pi-github |
9 | GitHub PRs, reviews, checks, issues, comments, and authentication | |
@parke.dev/pi-slack |
7 | Slack channels, threads, search, messages, and authentication | |
@parke.dev/pi-linear |
8 | Linear issue search, details, comments, states, transitions, and authentication | |
@parke.dev/pi-notion |
6 | Notion search, page reading, append, and authentication | |
@parke.dev/pi-integrations |
35 | One-install bundle for Git, GitHub, Slack, Linear, and Notion | |
@parke.dev/pi-dashboard |
— | Optional header/footer dashboard (cwd, model, full cost, tok/s, git, PR); off by default | |
@parke.dev/pi-openrouter |
— | CLI that syncs the full OpenRouter catalog into models.json, routing each model to its best-fit API surface, plus a benchmark harness that keeps the rules honest |
@parke.dev/pi-subagent lives in this monorepo and
provides the execution engine used by pi-workflows. Keeping both packages in
one workspace means their SDK boundary, tests, versions, and publish order are
validated together.
pi install npm:@parke.dev/pi-steel
pi install npm:@parke.dev/pi-background-terminals
pi install npm:@parke.dev/pi-sentinel
# …etc
# Install all productivity integrations together
pi install npm:@parke.dev/pi-integrationsGitHub, Slack, Linear, and Notion each provide a masked interactive setup
command: /github-login, /slack-login, /linear-login, and /notion-login.
Credentials are validated before being stored in
~/.pi/agent/integration-auth.json with 0600 permissions. Environment
variables take precedence, and GitHub reuses gh auth token when available.
For browser OAuth, use the providers' official hosted MCP servers through Pi's
native mcp.json configuration and pi mcp login: Linear and Notion support
ordinary interactive OAuth; Slack
requires a pre-registered Slack app/client identity. Avoid enabling both MCP
and the corresponding REST package unless duplicate tool surfaces are desired.
Each package's README documents its own configuration and prerequisites.
pi-steel needs a Steel instance, pi-firecrawl needs a Firecrawl API key or a
self-hosted instance, pi-workflows needs pi-subagent and a Node build with
--permission support. The rest work as-is.
Nothing requires configuration to start, and no package hardcodes a private
host. Where settings exist they resolve defaults ← ~/.pi/<name>.json ← environment,
and a malformed value falls back to its default rather than breaking startup.
See pi-ext-config for the shared loader.
Notable opt-ins:
- Dashboard — install
@parke.dev/pi-dashboard, then set"enabled": truein~/.pi/dashboard.json(orPI_DASHBOARD_ENABLED=true).
Tool previews, widgets and inspectors share Pi's native theme and width handling.
Expand tool results for diagnostics, bodies and artifacts; use /subagents and
/workflows for run details. The dashboard remains opt-in.
Subagent and workflow turns/spend are unbounded by default. Explicit per-run budgets remain enforced; workflow config ceilings are retired. Timeouts, cancellation, concurrency, nesting and permission controls remain in place. See presentation and migration details.
npm install
npm run check # typecheck + format check + tests
npm test
npm run pack:check # verify tarball contents for every package
npm run release:plan # show publish order and unpublished versionsPublishing uses package-scoped tags (pi-subagent-v0.7.0,
pi-workflows-v0.1.0). The release workflow publishes only the tagged package,
so independently versioned packages remain independent while CI and local
implementation stay consolidated. release:plan is dependency-ordered, and
release:publish refuses to publish a package until its workspace dependencies
at the requested versions are available on npm. The full release flow
(tag → CI → npm trusted publishing / OIDC) is in RELEASING.md.
See MIGRATION.md
for the current dependency-ordered release sequence, including the integration
libraries, individual providers, and bundle.
The repo is npm workspaces. Packages ship TypeScript source with no build step —
pi transpiles extensions on load, which is also why cross-package imports of
.ts files work.
Inspired by davis7dotsh/my-pi-setup, which showed what pi's extension API can do. These are independent implementations rather than forks.
MIT