task-factory
Tagline: *“Agentic work orchestrator that respects your time”*
Once users trust Pi enough, they wrap it in scripts, queues, worktrees, bots, and review lanes. This layer is the operational branch of the ecosystem.
This is the shortest explanation of what this layer is for and why it matters.
Once users trust the core loop, the ecosystem forks into automation patterns: queue-first orchestration, worktree swarms, JSON-mode scripting, RPC integrations, Slack bots, and web/TUI overlays.
These projects explain this branch of the ecosystem fastest.
Tagline: *“Agentic work orchestrator that respects your time”*
PiSwarm is a Shell-based orchestration toolkit for parallel GitHub issue and PR processing using the pi agent and Git worktrees.
ACP adapter for pi agent
These workflow slices connect the layer to real usage patterns.
A big part of Pi's distinctiveness is that it can stop being a chat app and become infrastructure for bots, scripts, or embedded tooling.
When a single session stops scaling, Pi users either wrap it in queue-first review lanes or in shell-native worktree swarms; both paths show up clearly in the ecosystem.
The layer-specific best-practice reminders that keep this branch legible.
There are at least two distinct Pi escalation paths: queue-first orchestration like Task Factory, and worktree-first shell swarms like PiSwarm. Pick the branch that matches how your team already works.