Pi TaskExec

Registre officiel Outils de développement

A host-agnostic MCP worker runtime for supervising local Pi coding-agent processes.

Que pouvez-vous faire avec Pi TaskExec ?

  • Runs tasks on local Pi using its locally configured default model, with optional per-worker model and thinking overrides.
  • Full worker lifecycle: spawn, status with bounded wait, steer, continue, cancel (pi_abort), and release (pi_release), plus list.
  • Read-only inspect (default) and read/write implement capability profiles.
  • The Supervisor chooses the working directory; the MCP verifies authorization but never creates worktrees or branches.
  • One unified MCP + pi-delegate Skill setup with keyboard multi-select across Codex, Zed, and OpenCode.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @zguiyang/pi-task-exec
Claude Code
claude mcp add pi-taskexec -- npx -y @zguiyang/pi-task-exec@0.4.0 mcp serve
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "pi-taskexec": {
            "command": "npx",
            "args": [
                "-y",
                "@zguiyang/pi-task-exec@0.4.0",
                "mcp",
                "serve"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Pi TaskExec
  2. Highlights
  3. Requirements
  4. Quick start
  5. Commands
  6. Learn more

Pi TaskExec

Pi TaskExec lets a supervising agent assign bounded, independent investigation, analysis, implementation, and verification tasks to local Pi workers through MCP. The agent can also work directly when delegation would add more overhead than value.

The project grew out of the author's own workflow: using different models or subscription plans for planning and review versus execution. If you also have multiple AI coding subscriptions or model resources, you can try this division of work to make better use of them and keep execution details from crowding the main agent's context.

The author is still evaluating how this approach affects context usage, total token consumption, and actual costs; savings are not guaranteed. It addresses the author's own collaboration needs and may help others with similar workflows. You're welcome to try it and share your experiences, alternative views, or suggestions via Issues.

English | 简体中文

Highlights

  • Runs tasks on local Pi using its locally configured default model, with optional per-worker model and thinking overrides.
  • Full worker lifecycle: spawn, status with bounded wait, steer, continue, cancel (pi_abort), and release (pi_release), plus list.
  • Read-only inspect (default) and read/write implement capability profiles.
  • The Supervisor chooses the working directory; the MCP verifies authorization but never creates worktrees or branches.
  • One unified MCP + pi-delegate Skill setup with keyboard multi-select across Codex, Zed, and OpenCode.

Requirements

  • Node.js >= 22.20
  • An installed and configured pi executable

Quick start

From the project you want to configure, run the unified setup:

npx -y @zguiyang/pi-task-exec@latest setup

v0.3.1 is the current published release. This checkout prepares v0.4.0 with updated delegation guidance and multi-host CLI flows. The v0.3.0 worker-interface changes still apply; if you are upgrading from v0.2.2, follow the v0.3.0 migration notes.

On a TTY it opens a keyboard multi-select for the hosts (codex, zed, opencode) plus a single scope (project or global), then runs and prints a concise result; a routine run does not print the full plan and does not ask for a Proceed? confirmation. Use --dry-run for the full plan (paths, conflicts, warnings) and --json for stable machine-readable detail. The pi-delegate Skill is installed from this repository (skills/pi-delegate) at the matching release tag through the pinned Skills CLI skills@1.7.1. Selections can also be given up front: --host may be repeated for several hosts, and exactly one --scope applies to the whole run:

npx -y @zguiyang/pi-task-exec@latest setup --host codex --host zed --scope project

Restart each selected host afterward, grant project trust if asked, and verify that pi_list is available inside the host.

Commands

npx -y @zguiyang/pi-task-exec@latest update
npx -y @zguiyang/pi-task-exec@latest uninstall
npx -y @zguiyang/pi-task-exec@latest doctor
npx -y @zguiyang/pi-task-exec@latest doctor --probe

setup, update, and uninstall share the same keyboard multi-select of hosts and one scope, and also accept repeated --host flags. update replaces the managed MCP entry and Skill files, so previously configured custom settings must be supplied again.

uninstall removes only the managed pi-task-exec MCP entries for the selected hosts and scope. The shared pi-delegate Skill is retained by default; it is removed only when that removal is explicitly requested, which prints a warning and reports the known hosts that still reference it first. For a non-interactive run, add --remove-skill to request that removal.

The existing add and remove subcommands (add mcp, add skill, remove mcp, remove skill) remain available as single-target commands. doctor is read-only; --probe checks the package runtime only and never creates a worker.

Learn more


English | 简体中文

Questions fréquentes

Qu'est-ce que Pi TaskExec ?

A host-agnostic MCP worker runtime for supervising local Pi coding-agent processes.

Comment installer Pi TaskExec ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add pi-taskexec -- npx -y @zguiyang/pi-task-exec@0.4.0 mcp serve. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Pi TaskExec ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Pi TaskExec est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Pi TaskExec ?

Il est publié par zguiyang. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.