Delegation is useful when a task has clear pieces that can be owned by different specialists. It is less useful when the parent silently decides what to hand off, or when a child runs somewhere the person cannot inspect. In Pi, pi-subagentura is built around making that handoff visible and steerable.

Routing guidance, with the person still in charge

I made the extension's --orchestratorv2 mode give the parent agent routing guidance: send clear work to attachable interactive subagents, ask when a request is ambiguous or a narrow request has no matching specialist, and leave specialist repository work to the child that owns it. Broad work can be decomposed into new children. You can also provide your own agent profiles and tell Pi when to use them. Your prompts, models, and choice about how much to delegate remain yours.

This is prompt-guided behavior. It does not technically disable the parent agent's other tools or guarantee that every eligible task will be delegated. That distinction matters: routing instructions can shape the default behavior, but they are not an enforcement boundary. If a workflow needs a repeatable scripted sequence, a saved code workflow can express that sequence. Neither the router nor the workflow VM is a security boundary.

Make the work inspectable

Interactive subagents run as separate Pi sessions in supported terminal multiplexers. You can watch their activity, inspect captured output, attach to a session, send a follow-up, or cancel it. For lighter work, the extension also offers in-process delegation. These are different execution choices: a separate session gives you a place to inspect and continue the child conversation, while an in-process job avoids starting another Pi session.

Visibility is useful even when it cannot identify the cause of a stall. A quiet child could be waiting on a model response, an external tool, or still doing work. The extension exposes controls and recorded state; it does not infer that inactivity means failure or automatically terminate every quiet child.

Choose the right mode for the work

Use --orchestratorv2 when you want an interactive parent to route work to specialists or create children for broader tasks. Use the workflow-oriented --orchestrator mode or /workflow when the process itself should be a reusable script: code defines which agents run, how results move between stages, and when the workflow is complete. The router chooses where a request goes; a workflow defines a repeatable program.

pi --orchestratorv2

# Or add your own routing instruction:
pi --orchestratorv2 --append-system-prompt \
  'Use my specialist profiles in ./agents when delegating.'

The example adds guidance; it does not create a hard rule. See the router documentation and the terminal session guide for setup and operation details. The implementation's routing prompt source contains the routing instructions themselves.

Try a small handoff first

Install pi-subagentura, start with one bounded task, and decide whether you want a child Pi session or lightweight in-process work. Keep the task and ownership clear, then inspect the result before expanding the delegation. The project overview has installation steps, workflow documentation, and a recorded demonstration.