Continue GitHub Copilot app session in VS Code
Move a Copilot agent session to VS Code with conversation, code, and context intact.
- Open the session you want to continue in the GitHub Copilot app.
- Select 'Open in VS Code' from the session.
- Review the diff in VS Code's Source Control view.
- Continue prompting Copilot in the sidebar for clarification or revisions.
- Edit files directly in VS Code for manual adjustments.
- Run the project's validation workflow using the integrated terminal.
- Test the changes locally, including in a browser if applicable.
- Commit and push the changes using VS Code's Source Control view or terminal.
What it does and when to use it
Seamlessly transition a GitHub Copilot app session into Visual Studio Code. This workflow preserves the entire conversation, code changes, and working context, allowing for detailed review, manual edits, and local testing without restarting or losing progress.
Why it works
The integration creates a connected worktree and displays the existing session in the VS Code sidebar. This maintains the context, allowing you to continue the conversation and build upon the agent's work directly within your editor.
Sources and credit
- How to continue a GitHub Copilot app session in VS Code ↗GitHub Blog · GitHub Blog: Copilot · Oct 19, 2026 · paraphrased
First seen on Subvolts Oct 19, 2026. Updated Oct 19, 2026. Spotted a problem? Tell us.
Where it shows up
- How to continue a GitHub Copilot app session in VS CodeMicrosoft · GitHub Blog: Copilot · Oct 19, 2026
Related in the PlaybookPlaybook →
The Playbook: reusable how-tos, prompts, configs and tips pulled out of the news.
- ChecklistReviewing Copilot-generated code in VS CodeChecklist for inspecting and verifying code changes made by GitHub Copilot. · 10 min
- Skill or agent configCustom repository rules for Codex Code Review in AGENTS.mdDefine custom rules in AGENTS.md to guide Codex Code Review for specific repository conventions and issues. · 15 min
- RulePreserve experimental notification names for backward compatibilityDo not rename experimental notifications if consumers rely on them. · 5 min
- Prompt patternUse Codex to explain pull requests and code sectionsLeverage Codex with the gh command to get summaries and explanations of code changes and features. · 5 min
- ChecklistEvaluating Codex Code Review rule effectivenessCheck if Codex surfaces intended violations, avoids false positives, catches bugs, and cites guidance correctly. · 30 min
- ToolCodex Code Review with custom repository rulesAI-powered code review that uses custom rules defined in AGENTS.md for better convention adherence. · 15 min
Questions people ask
- Which AI tools does this work with?
- The sources used it with Copilot.
- Where did this come from?
- GitHub Blog (GitHub Blog: Copilot). Subvolts collected, normalized and credited it; the link above opens the original.