You can move a GitHub Copilot app session into VS Code without starting over

• the session context: the task, the plan and the conversation, shown in the Copilot sidebar
• the diff: the files and lines the agent changed, ready to review in Source Control
• the worktree: the same isolated working tree the session used

You can keep prompting Copilot in the same conversation, edit files by hand, and run your tests in the integrated terminal. Because VS Code is on the session's branch, pushing updates the pull request that already tracks the work. No copying files or re-explaining the task.

Who it's for. People who let an agent do the first pass but want to review the diff, fix a few lines and run the project locally before shipping.

What you need. The Copilot app and VS Code signed in to the same GitHub account, a session with code changes, and permission to push to the repository. On Copilot Business or Enterprise, GitHub says an admin must have the Copilot CLI enabled in policy settings before you can use the app.

The caveats.

• This is a walkthrough GitHub published on Oct 19, not a brand-new feature.
• Pushing updates the existing pull request, so review the agent's diff and run tests before you push.
• If you skip the button and look for the session in VS Code's sessions list instead, VS Code's docs say Copilot only finds supported local sessions updated in the last seven days, and external sessions are filtered by the External setting (default: last 7 days).
• A worktree keeps file changes apart from your main checkout. It does not, on its own, isolate things like a local database or a dev server port. That part is still on you.

Disclosure: Not tested by MODEL. Not sponsored. No affiliate links.

MODEL Editors