GitHub Copilot with Git Worktree

Does Copilot Support Worktrees?

Yes. GitHub Copilot works in any directory that is part of a git repository, including worktree directories. When you open a worktree in VS Code or another supported editor, Copilot detects the git context automatically and provides completions based on the files in that worktree.

Copilot does not need to know that a directory is a worktree rather than a regular clone. From Copilot's perspective, it is working with a normal project directory that happens to have a .git file (instead of a .git directory) pointing to the main repository. This distinction is transparent to Copilot and to your editor.

The one caveat: Copilot's context window includes files from the currently open workspace. If you have multiple worktrees open in separate editor windows, each Copilot instance builds context from its own workspace's files, which is exactly the behavior you want for isolated development.

Using Copilot in Worktree Directories

The setup is the same as using Copilot in any project: open the worktree directory in your editor and start coding. Copilot provides completions based on the files and branch in that worktree.

# Create a worktree for your feature
git worktree add ../my-project-feat-search -b feat/search

# Open it in VS Code (Copilot activates automatically)
code ../my-project-feat-search

# Or open in another editor window alongside your main checkout
# Each window gets its own Copilot context

When using Copilot Chat in a worktree, the chat context includes files from the worktree's branch. If your feature branch has new files that do not exist on main, Copilot Chat can reference them. If the main branch has files not in your worktree (because you deleted them in your feature branch), Copilot will not suggest them.

This branch-aware context is one of the advantages of using worktrees with Copilot: each editor window provides Copilot with the right context for its task.

Copilot CLI and Worktrees

GitHub Copilot in the CLI (gh copilot) works in any directory, including worktrees. You can use it to explain commands, suggest fixes, or generate shell scripts, all within the context of a specific worktree:

# Navigate to a worktree
cd ../my-project-feat-search

# Use Copilot CLI for suggestions
gh copilot suggest "write a test for the search function"

# Explain a git command
gh copilot explain "git worktree list --porcelain"

# Get help with a command
gh copilot suggest "find all files changed between this branch and main"

Copilot CLI uses your current directory as context for its suggestions. When you run it inside a worktree, it picks up the files and git state of that worktree, giving you relevant suggestions for the task at hand.

Workspace Configuration

When using multiple worktrees with Copilot, workspace settings ensure a consistent experience across all worktrees:

Shared Settings via Git

Settings stored in .vscode/settings.json are tracked by git and automatically available in every worktree. This is the best place to configure Copilot workspace-level settings:

{
  "github.copilot.enable": {
    "*": true,
    "markdown": true,
    "plaintext": false
  },
  "github.copilot.advanced": {
    "length": 500
  }
}

Per-Worktree Overrides

If you need different Copilot settings in a specific worktree (for example, disabling Copilot for a security-sensitive branch), you can override the workspace settings by creating or modifying the .vscode/settings.jsonin that worktree's branch. Since each worktree has its own branch, those changes stay isolated.

Multi-Root Workspaces

You can open multiple worktrees in a single VS Code window as a multi-root workspace. This lets Copilot see files from all worktrees in its context, which can be useful for cross-referencing but may also introduce noise:

{
  "folders": [
    { "path": "../my-project-main" },
    { "path": "../my-project-feat-search" },
    { "path": "../my-project-fix-auth" }
  ],
  "settings": {
    "github.copilot.enable": {
      "*": true
    }
  }
}

For most workflows, separate windows per worktree give cleaner Copilot suggestions because the context is focused on one task.

Tips