Pi has no official Subagents, but 4 community extensions emerged; author shares extension stack order

solyarisoftware · x · 2026-10-09

Pi coding assistant ships without Sub-agents or Plan Mode, but Mario (badlogic) open-sourced his personal pi-subagent extension, running each subagent in an isolated tmux session with suspend/resume and full transcript on restart. It's unofficial and unsupported.

The community now offers four main options:

badlogic/pi-subagent: tmux-based isolation; best for tmux users doing independent reviews and debugging.
nicobailon/pi-subagents: 580k monthly npm downloads, ships with reviewer/scout/oracle roles, callable in plain language—best out-of-box experience.
tintinweb/pi-subagents: mirrors the Claude Code experience; existing Claude Code workflow scripts run as-is; nesting off by default.
championswimmer/pi-subagent-manager: blends Claude Code agent types with Codex-style path trees (e.g. /root/fix-auth/review), supports parallelism, nesting, and restart recovery; requires Pi 0.99.2+.

Caveat: install only one—mixing subagent extensions causes conflicts.

The quoted thread argues you should layer extensions in order: run real tasks manually first to find bottlenecks → codify repeated steps into Skills (no code needed) → add Extensions only when behavior must change at runtime (tools, commands, event listeners) → package into a distributable Package only once the combo is stable. Since Packages execute code with full Pi system privileges and Skills can induce command execution, audit anything before installing.

Original post →

Pi has no official Subagents, but 4 community extensions emerged; author shares extension stack order

More from coding & agent