Skip to content

06 — Subagent / Task dispatch parity for pi #526

Closed

Description

@gewenyu99

Epic: #520 · Behavior change: none (default-off) · Depends on: #525

Summary

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

  1. changed the title [-]06 — Subagent / `Task` dispatch parity[/-] [+]06 — Subagent / Task dispatch parity across runners[/+] on Jun 5, 2026
  2. changed the title [-]06 — Subagent / Task dispatch parity across runners[/-] [+]06 — Subagent / Task dispatch parity for `pi`[/+] on Jun 19, 2026
  3. gewenyu99 commented on Jul 3, 2026

    @gewenyu99
    CollaboratorAuthor

    Done in #701 — pi has task/todo tools and controlled dispatch_agent (fenced, read-only, non-recursive), parity with the anthropic path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions