My pi setup for coding agent workflows.
Important
This setup is built for pi.nvim. Some extensions (notably permission) rely on the Neovim plugin for UI interactions like edit reviews. Using this package with the pi TUI will most likely require adjustments.
- context —
/contextcommand for session introspection - fetch —
fetchtool for retrieving URLs as markdown - mcp — MCP server integration
- permission — tool execution control with allow/deny/ask rules
- rules — rule files injected into system prompt
- web-search —
web_searchtool via Brave Search API
workflows/ contains reusable workflows for Epics, Tasks, and Gigs:
/project-setup— interactively configure artifacts, branches, optional integrations, and policies;/epic— plan and maintain an initiative of prospective Tasks;/task— initialize or resume work belonging to one Epic;/gig— initialize or resume standalone work;/backlog— optional integration-only future-work intake;/todo— optional integration-only ready-work intake.
Authoritative .project/ artifacts use either versioned or unversioned Git policy; unversioned mode excludes them from Git and never projects workflow-system traces. Optional tracker support includes GitHub or Linear; optional forge support currently uses GitHub. Runtime provider operations use Pi-registered MCP tools through the same permission extension as every other agent. Guided setup may additionally inspect Linear and provision an explicitly approved GitHub Project through credential-isolated direct APIs. See the workflow setup and artifact guide.