1 seamless switch: GitHub Copilot agents bring web session plans and chat to VS Code

GitHub published first-hand research detailing how developers can continue a GitHub Copilot application session directly within Visual Studio Code. This update allows users to move their work from the web-based interface to their local editor without losing the conversation, code changes or working context. The feature aims to streamline the workflow between automated agent tasks and manual developer review.

The process begins when an agent finishes the bulk of a change. Users can select the option to open the session in VS Code. If multiple editors or installations are detected, the user chooses the preferred one. The editor then opens the project using the specific worktree associated with the session. The existing session appears in the Copilot sidebar, keeping the task, plan and conversation available for reference.

Context preservation details

The session contains more than just modified files. It records the task, the plan and the conversation that produced the changes. This context helps developers understand why the agent chose a particular implementation. Users do not need to summarize the history or copy it into a new chat. The preserved conversation allows developers to ask Copilot to revise part of the work or explain unclear decisions.

Who is affected

This feature targets developers who use GitHub Copilot for coding assistance. It benefits teams that rely on the agent for repetitive or time-consuming tasks but require manual inspection for final adjustments. By keeping the worktree and session connected, developers can edit files directly in VS Code. Manual changes build on the agent’s work without requiring file copying or branch recreation.

Defender's checklist

Developers should inspect the diff in VS Code before editing. Open the Source Control view to see changed files and review them line by line. Check that the implementation follows repository conventions and handles error states. Verify that no unrelated files were modified. Use the integrated terminal to run the project’s validation workflow and tests. Treat agent-generated changes like code written by a person.

Operational impact

Organizations should assess how this workflow change affects their code review processes. Teams usually need to update documentation to reflect the new handoff between web and local environments. Managers should verify that developers understand how to review agent-generated diffs effectively. Check whether existing security scanning tools integrate properly with the VS Code worktree. Ensure that staff know how to use the preserved conversation to audit decisions.

What to do and how to stay safe: GitHub

• Review agent-generated code changes in the local editor before merging them into the main branch.
• Verify that the preserved conversation context aligns with the actual code modifications made.
• Run standard validation workflows and tests in the integrated terminal to catch errors.
• Monitor for any unexpected file modifications outside the intended scope of the task.

Step-by-step guide: Implementing AI Usage Policies at Work: A Step-by-Step Framework

General security guidance from the InfoSec Ledger newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

Does the session lose its history when moved to VS Code?

No, the session preserves the task, plan, conversation and code changes when opened in VS Code.

Do I need to copy files to continue working?

No, VS Code opens the same isolated worktree used by the session, so no copying is required.

Can I make manual edits after the agent finishes?

Yes, you can edit files directly in VS Code, and changes build on the agent’s existing work.