GitHub just opened the floodgates on its GitHub Copilot app. The waitlist is gone. The technical preview is now available to all existing Copilot Pro, Pro+, Business, and Enterprise customers. This is not another IDE plugin or a chat sidebar -- it is a fundamentally different kind of tool.

This is not an IDE extension. It's a new interface category: a control center for managing multiple parallel agent sessions, each running in its own isolated git worktree. The pitch is simple: your agents are already doing more work per session, so the bottleneck has shifted from writing code to managing the agents writing it. The Copilot app is built around that new reality.

The problem it's solving

While the agentic shift has made development faster, it's also led to disjointed workflows, more context switching, and too much time spent reviewing agent-generated code. If agents are going to be a durable part of how software gets built, they need a real place in the developer workflow. Yet most developer tools were not designed for directing multiple agents in parallel.

Context scatters across windows. You lose track of what's running. Code lands in pull requests without a clear trail of what the agent tried, what it validated, or where human judgment is needed. The Copilot app is GitHub's answer to all three of those problems at once.

How it actually works

Every session runs in its own git worktree -- a real, isolated copy of your branch. This helps parallel agent sessions work without stepping on each other. The app handles every worktree for you: no manual setup, no cleanup, no branch juggling. A git worktree, for context, is a way to check out multiple branches of the same repo simultaneously at different paths on disk -- the app automates all of that behind the scenes.

The central hub is the My Work