GitHub Copilot CLI Adds Isolated Worktree Sessions
GitHub CopilotGitHub Copilot CLI added an experimental /worktree command that spins up an isolated Git worktree and a separate conversation without disturbing a developer's active session. The feature extends the git worktree isolation pattern GitHub already uses for agent sessions in VS Code to the terminal, and ships alongside a new Sessions sidebar and a Git-independent /rewind command as part of the CLI's August 3, 2026 weekly update.
Key Takeaways
- The
/worktreecommand creates an isolated Git worktree and opens a separate Copilot CLI conversation, letting developers experiment without disrupting their main session. - It ships as an experimental feature, so behavior and command flags may still change before general availability.
- The feature mirrors VS Code's Agent Host isolation model, extending the git worktree isolation pattern GitHub introduced for VS Code agent sessions to the terminal.
- It complements the CLI's new Sessions sidebar, giving power users two distinct tools for managing parallel work: session switching and workspace isolation.
- No manual
git worktree addcommands are required — Copilot CLI handles worktree creation and conversation scoping automatically. - The rollout targets developers running long, branching agentic tasks who previously had to script their own worktree-and-reattach workflow.
New /worktree Command Isolates Copilot CLI Sessions
GitHub Copilot CLI introduced an experimental /worktree command as part of its August 3, 2026 weekly release, giving developers a fast way to spin up an isolated Git worktree and start a fresh conversation without touching their active session.
What the Command Does
Running /worktree from inside a Copilot CLI session creates a new Git worktree and drops the developer into a separate conversation scoped to that workspace. Because the new workspace is fully isolated from the primary checkout, Copilot can explore a different branch, try out an alternative implementation, or investigate a fix in parallel — all without disturbing files or conversation history in the original session.
Why It Matters
Developers running long agentic sessions in the terminal have increasingly needed a way to branch off and experiment without losing progress on the task at hand. Manually creating worktrees and re-attaching Copilot CLI to each one was the only option until now. Folding worktree creation directly into a slash command removes that friction and mirrors the isolation model GitHub already ships for Copilot, Claude, and Codex sessions inside VS Code's Agent Host.
Availability
The /worktree command is available now to anyone running the latest Copilot CLI as an experimental feature, alongside a refreshed Sessions sidebar for managing multiple concurrent sessions and a /rewind command that no longer requires Git to restore changes.