copilot-delegate

Copilot Delegate

When to Use

• You want to delegate a bounded coding task to a separate copilot implementer (GitHub Copilot CLI) and then review its diff yourself.
• The user explicitly asked for delegation to this implementer.

You are the orchestrator. Delegate a bounded coding task to a separate implementer — the GitHub Copilot CLI — then review what it produced and land it yourself. You write the brief and own the judgment; the implementer makes changes in its own session in a clean working tree; you verify and commit.

The loop needs only a shell command and file access, so any comparable orchestrator can drive it.

When NOT to use this

• The task is small enough to do inline; delegation overhead is not worth it.
• The copilot CLI is not installed or authenticated.
• You need a hard sandbox. Copilot exposes sandbox controls, but they are upstream-experimental

(MXC-based, controlled via the /sandbox command and settings, disabled by default) — this relay does not configure them. --read-only only disables edit tools (--mode plan); shell commands still run. If project files must not change at all, dispatch against a clean or isolated worktree.

Prerequisites (check once)

1. Install copilot (npm install -g @github/copilot; the CLI requires Node 22+, the relay

itself runs on Node 18+ — the relay probes copilot version).

2. Authe