GitHub Copilot: Git Worktree Isolation Expands to Claude and Codex in VS Code
GitHub CopilotVS Code's July 2026 releases introduced a dedicated Agent Host process that runs Copilot, Claude, and Codex agent sessions outside the editor window, letting the same session be connected to and rendered from multiple VS Code windows at once. Building on that architecture, Git worktree isolation — previously available only to Copilot sessions — now extends to Claude and Codex sessions too, so developers can run parallel agents on different branches of the same repository without them interfering with the main workspace.
Key Takeaways
- VS Code introduced a dedicated Agent Host process (via the new Agent Host Protocol) that runs Copilot, Claude, and Codex sessions independently of any single editor window.
- Because sessions now live outside the window process, they can be connected to and rendered from multiple VS Code windows at once, and survive closing and reopening a window.
- Git worktree isolation, previously exclusive to Copilot, now also covers Claude and Codex agent sessions.
- Developers can run multiple parallel agent sessions on different branches of the same repo — mixing Copilot, Claude, and Codex — without conflicts in the main workspace.
- The same update added risk-based tool-call approvals, auto-approving low-risk actions to reduce prompt fatigue in long sessions.
- The Agents window also gained file-level diff statistics and a more compact multi-file diff layout for faster review.
Sources & Mentions
4 external resources covering this update
A New Agent Host Architecture
Starting with VS Code 1.129 (released July 15, 2026), Microsoft rearchitected how agent sessions run in VS Code. Instead of living inside a single editor window's process, agent sessions now run in a dedicated Agent Host — a separate process that hosts agent harnesses including Copilot, Claude, and Codex, coordinated through the new Agent Host Protocol (AHP). Because a session now lives in its own process rather than being tied to one window, the same running session can be connected to and rendered from multiple VS Code windows simultaneously. Developers can close a window and reopen it with the session still intact, or open a second window pointed at the same in-progress session.
Worktree Isolation Extends Beyond Copilot
Git worktree isolation — where an agent's changes are kept in a separate working copy of the repository rather than the developer's active branch — had previously been available only to Copilot agent sessions. With VS Code 1.130 (released July 22, 2026), that isolation now covers Claude and Codex sessions as well, since all three harnesses run through the same Agent Host. In practice, this means a developer can kick off three parallel agent sessions targeting three different branches or features in the same repository, using any mix of Copilot, Claude, or Codex, and each one works in its own isolated worktree without stepping on the developer's active working copy or on each other.
Smarter Approvals and Review Alongside the Change
The same release also refined the surrounding workflow: tool-call approvals now factor in an assessed risk level, so low-risk actions can proceed automatically while only genuinely risky actions still prompt for confirmation, cutting down on approval fatigue during long agent sessions. The Agents window also picked up file-level diff statistics and a more compact multi-file diff layout to make reviewing an agent's changes faster.
Why It Matters
Together, the Agent Host and its extended worktree support mark a shift in how VS Code treats agent sessions — less like a chat panel bolted onto the editor, and more like an independent, resumable, parallelizable workflow that happens to render inside the editor. For teams already running multiple coding agents side by side, this removes one of the more common sources of merge conflicts and stepped-on changes.