You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bring subagent / Task behavior to the pi runner (or explicitly gate it where unsupported), matching the anthropic path's wizard-variant=subagents behavior. Subagents inherit the same runner; they are not a
separate router.
Scope
Map the Task store tools (TaskCreate/Update/Get/List) + TUI todos to pi (reuse shared tools).
Subagent dispatch: implement via Pi's mechanism or, if not viable yet, disallow the dispatch tool on pi
and document.
Ensure disallowed tools don't leak into subagents (the gap that bit anthropic).
Acceptance criteria
Task todos render in the TUI under pi.
Subagent parity (or a documented, gated no-op) verified.
Files
src/lib/agent/runner/shared/, runner/backends/pi/
Notes
The orchestrator router (#520) is a different axis from in-runner subagents: the router decomposes a
program into leaves and resolves a pair per leaf, whereas a subagent runs inside a single leaf's runner.
Activity
[-]06 — Subagent / `Task` dispatch parity[/-][+]06 — Subagent / Task dispatch parity across runners[/+][-]06 — Subagent / Task dispatch parity across runners[/-][+]06 — Subagent / Task dispatch parity for `pi`[/+]gewenyu99 commentedon Jul 3, 2026
Done in #701 — pi has task/todo tools and controlled
dispatch_agent(fenced, read-only, non-recursive), parity with the anthropic path.