I Shipped 6 Upgrades to My Copilot CLI Orchestrator. The SDK Had Other Plans.

Six weeks ago I had a working orchestrator for GitHub Copilot CLI. It ran agents in parallel on isolated branches, verified their output against transcripts, and merged what passed. 947 tests. Zero...

By · · 1 min read
I Shipped 6 Upgrades to My Copilot CLI Orchestrator. The SDK Had Other Plans.

Source: DEV Community

Six weeks ago I had a working orchestrator for GitHub Copilot CLI. It ran agents in parallel on isolated branches, verified their output against transcripts, and merged what passed. 947 tests. Zero TypeScript errors. Solid. Then I looked at what Copilot CLI shipped since GA and realized the tool was already falling behind the platform. Fleet mode, hooks, plugins, MCP servers, the /pr command. The CLI had grown a surface area that my orchestrator was either duplicating or ignoring. So I planned six upgrades, built all six, and ran live integration tests against real Copilot CLI sessions, real GitHub PRs, and real MCP client connections. Some things worked exactly as designed. One thing didn't work at all, and the reason is worth knowing if you're building anything on top of Copilot CLI's hook system. Here's what happened. moonrunnerkc / copilot-swarm-orchestrator Verified, quality-gated orchestration for GitHub Copilot CLI. Every agent proves its work before anything merges. Copilot Swa