Pi Subagent Extensions Compared

Start with how you want to work.

This guide is maintained by the creator of pi-subagentura, which is one of the options below. It compares selected projects using their own public documentation, checked on 2026-10-21. This is a documentation comparison, not a hands-on benchmark or a complete directory; it makes no claims about popularity, quality, speed, or reliability. Features can differ between the reviewed source and a package you install.

Work in a specialist’s terminal. pi-subagentura and HazAT’s pi-interactive-subagents launch interactive Pi sessions in supported terminal environments.
Manage specialists inside Pi. The other projects offer different combinations of in-process sessions, child processes, live status, transcript viewers, steering, and continuation. Check the execution and workspace rows below.
Separate execution from workspace. A child process does not automatically get its own Git worktree. The comparison distinguishes tools that create worktrees from those that accept or require a working directory.

Several projects share the name “pi-subagents.” Publisher names and package commands below distinguish them. The pi-subagentura project statistics are separate from this feature comparison.

Compare execution, interaction, and workspace.

Each row summarizes what the project documents. Follow an extension name for context, continuation, install command, and pinned source. On a narrow screen, scroll the table horizontally.

Documented execution, terminal interaction, and workspace behavior for selected Pi subagent extensions
Extension	Execution	Where you work	Workspace
lmn451/pi-subagentura · this project	Interactive subagents run as separate Pi processes; other tool groups offer in-process calls.	Attachable child panes in tmux, Zellij, or Herdr; inspect, focus, and message the child directly or through the parent.	Choose a working directory or worktree yourself; interactive launches do not create Git worktrees.
HazAT/pi-interactive-subagents	Each specialist runs as a separate Pi session in a multiplexer pane.	Work in a cmux, tmux, Zellij, or WezTerm child pane; the widget tracks status and the session can be resumed.	Set a child working directory as needed; automatic Git worktree creation is not documented.
nicobailon/pi-subagents	Foreground children run in the parent Pi process; background children run in a detached runner.	Use parent TUI progress and FleetView to inspect, steer, or stop runs; no multiplexer pane is required.	Workflow agents can use optional worktree isolation; foreground and background runs use their documented execution modes.
tintinweb/pi-subagents	Agents run as Pi sessions in the host process; there is no multiplexer requirement.	Use Pi's widget, FleetView, transcript viewer, or @handle mentions to inspect and continue work.	Optional worktree isolation uses a repository copy and commits changes to a branch on completion.
mjakl/pi-subagent	Delegations normally use separate Pi processes; experimental parent-local inline workers are also available.	Headless children stream progress and results in the parent Pi interface; inline workers run locally in the parent session.	Separate processes use the selected project context; automatic Git worktree creation is not documented.
gotgenes/pi-subagents	Child sessions run in the host Pi runtime; the core package does not spawn subprocesses.	Foreground results stream inline; use the widget for background runs, steering tools, or the transcript viewer.	Install the companion worktrees package for optional temporary Git worktrees with branch-saved changes.
Integralist/pi-subagents	Subagents are nested Pi AgentSession instances inside the host process.	Navigate the live agent list, inspect and steer a full-screen child conversation, or message and resume a named agent with @handle.	Workspace isolation is not described in the project README; children are nested sessions in the host process.
AlexParamonov/pi-subagents-lite	Child AgentSession instances run in the host Pi process; no multiplexer pane is required.	Use the live widget and conversation viewer to inspect, steer, stop, or continue agents from Pi.	Supply `worktree_path` to target an existing checkout or linked worktree; the tool does not create one.

Extension details and sources.

lmn451/pi-subagentura · this project

Good fit: Published v4.0.1: interactive terminal sessions, direct specialist follow-ups, or optional parent-guided routing.
Requirements and tradeoffs: Interactive sessions require tmux, Zellij, or Herdr. Orchestratorv2 guides routing through a system prompt; it does not enforce a deterministic route.
Interaction: Inspect child terminals, focus a pane, attach from another terminal, and follow up with the child directly or through its parent.
Context and continuation: A child can start fresh, inherit parent context, or receive an explicit handoff. Interactive state recovers with its matching parent session; /new and /fork clean up owned panes.
Process and workspace: Interactive children are separate Pi processes. They do not create Git worktrees automatically; choose a working directory or worktree separately.

pi -e npm:pi-subagentura

Repository · Documentation (644387d5a60db88aa07f743473dbb5b1993ad013)

HazAT/pi-interactive-subagents

Good fit: Asynchronous specialist panes, reusable agent definitions, and bundled planning and iteration flows.
Requirements and tradeoffs: Pi must run inside cmux, tmux, Zellij, or WezTerm; agent behavior and defaults are configured through agent files.
Interaction: A live widget tracks pane status; interrupt active turns, resume prior sessions, or work directly in a child pane.
Context and continuation: Standalone starts fresh by default; `fork: true` seeds the child with the caller's conversation. Resuming continues its saved session.
Process and workspace: Each child runs in a dedicated multiplexer pane, with a configurable working directory such as an agent role folder.

pi install git:github.com/HazAT/pi-interactive-subagents

Repository · Documentation (c100577ebf7393a11d098ad9810ec6c269dcfc30)

nicobailon/pi-subagents

Good fit: Broad delegation toolkit with FleetView controls, reusable workflows, and background jobs.
Requirements and tradeoffs: Requires Pi 1.2.0 or newer; includes workflow, schedule, watchdog, and external-runner features alongside delegation.
Interaction: Foreground children stream in the parent TUI; background runs stay visible in FleetView, where you can inspect, steer, or stop them.
Context and continuation: Children have their own sessions. Prompts can use the current discussion; workflow results can stay outside parent context until delivery.
Process and workspace: Foreground children run in the parent Pi process, while background children use a detached runner. Optional worktree isolation is available for workflow agents.

pi install npm:pi-subagents

Repository · Documentation (80f8f79d51ee8075fd39baf7fe8ff36b43c3a790)

tintinweb/pi-subagents

Good fit: Claude Code-style agent definitions, FleetView, conversation steering, nested delegation, and scripted workflows.
Requirements and tradeoffs: Requires Pi 1.1.0 or newer. Worktree isolation is optional; model-scope enforcement is configurable.
Interaction: Manage agents in Pi's widget, fleet list, conversation viewer, or `@handle` mentions; send steering messages and resume completed sessions.
Context and continuation: Parent context can be forked into a child. Saved sessions can resume later, and agent memory supports project, local, or user scope.
Process and workspace: Optional worktree mode runs an agent in a repository copy and preserves changes on a branch; separate tool and extension policies are configurable.

pi install npm:@tintinweb/pi-subagents

Repository · Documentation (ca93a5247e72e7053fcd10bea7125d6c4205f949)

mjakl/pi-subagent

Good fit: Markdown-defined specialists, parallel calls, streaming progress, and named continuation sessions.
Requirements and tradeoffs: Requires Pi 0.87.1 or newer; parent-local inline workers are explicitly experimental.
Interaction: Headless child processes stream progress and results through the parent Pi interface; named specialists can be called again for follow-up work.
Context and continuation: Children start fresh by default; an explicit option clones the parent's current conversation. Named sessions preserve a specialist's follow-up history.
Process and workspace: Each delegation normally runs as a child Pi process; parent-local inline workers are an experimental option. Depth and cycle guards are available.

pi install npm:@mjakl/pi-subagent

Repository · Documentation (77cc8be9a4257c00643f328d461a7ab2c1490686)

gotgenes/pi-subagents

Good fit: In-process child sessions with live status, agent-defined tools and models, steering, resume, and a typed extension API.
Requirements and tradeoffs: Worktree isolation is provided by the separate @gotgenes/pi-subagents-worktrees package.
Interaction: Foreground results stream inline; a persistent widget tracks background agents. Use steering tools to redirect a run and a read-only viewer for transcripts.
Context and continuation: Each agent has its own session context. Parent-context inheritance is optional, and completed sessions can be resumed from their transcripts.
Process and workspace: Nested Pi AgentSession instances run in the host process; the companion worktrees package can provide Git workspace isolation.

pi install npm:@gotgenes/pi-subagents

Repository · Documentation (41405de895fb53f802df89f8978456cd1dae397e)

Integralist/pi-subagents

Good fit: In-process specialists with live full-screen transcript controls, direct @mentions, and reusable Markdown agent files.
Requirements and tradeoffs: Child sessions load without extension tools, which prevents nested subagents.
Interaction: Navigate the live agent list, inspect and steer a full-screen child conversation, and message or resume a named agent with `@handle`.
Context and continuation: A child has its own prompt and context window; persistent transcript files let a resumed agent continue its conversation history.
Process and workspace: Subagents are nested Pi AgentSession instances inside the host process, not spawned child processes.

pi install git:github.com/Integralist/pi-subagents

Repository · Documentation (37e9c2a02873bd9733971bd529f12e53d9d40112)

AlexParamonov/pi-subagents-lite

Good fit: Four tools for foreground and background agents, steering and continuation, custom models, and worktree targets.
Requirements and tradeoffs: Requires Pi trust approval for some cross-repository worktree targets; the default system-prompt mode replaces the parent's prompt.
Interaction: A live widget and conversation viewer show agent activity; use `/agents` to steer, continue settled agents, stop runs, or spawn manually.
Context and continuation: Prompt mode is configurable as replace, inherit, or custom. AGENTS.md context files load by default.
Process and workspace: `worktree_path` targets an existing checkout or linked worktree, including another repository subject to Pi's project-trust rules.

pi install npm:pi-subagents-lite

Repository · Documentation (0a3fb576416398995d82ebc6ecd7f1cb5b5ea2de)

Ask these questions before you install.

Where will you intervene? Opening a terminal pane, steering from a transcript viewer, and sending another tool call are different ways to continue a task. Try the path you will use most.
Which context should a child receive? A fresh session, a fork of the conversation, and an explicit handoff make different information available. Check defaults as well as optional modes.
Can two agents edit safely? A separate process does not imply a separate checkout. Confirm whether the extension creates a worktree, uses an existing path, or shares the parent’s working directory.
What survives the parent? Continuation within one session and recovery after restarting Pi are separate capabilities. Read the lifecycle rules before relying on saved work.
How much coordination do you need? A focused delegation tool can be enough for one review. Reusable workflows, nested agents, schedules, and fleet controls add capabilities to configure and supervise.

For peer sessions working as a team, also see pi-messenger. Its shared-workspace messaging and coordination address a related need; it is not included in the parent-to-subagent comparison above.

Scope and disclosure. The page is published by the pi-subagentura maintainer, so one listed project is the publisher’s own. Each documentation link is pinned to the audited commit, including the README from the pi-subagentura v4.0.1 source commit. The audit reads project-published sources; it does not test the extensions or certify that every described behavior works in every environment. Recheck the selected project’s current release notes and Pi requirements before installing. The table is categorical and does not rank projects.

Try a workflow you can inspect.

For pi-subagentura, start with the installation guide, then open specialists in tmux or Zellij. The parallel code review guide gives two specialists distinct scopes and shows how to follow up on their findings.

Watch the recorded workflow to see the extension operating in Pi before you try it.