GitHub Copilot sessions now open in VS Code, worktree intact

The tutorial is framed around a common handoff point: the agent has finished the bulk of a change, and the developer wants to inspect one implementation detail, adjust a few lines by hand, and run the project locally. GitHub's answer is to keep the original session rather than reconstruct it in a new editor window.

Mechanically, selecting Open in VS Code opens the project using the worktree associated with the session and shows the existing session in the Copilot sidebar. That keeps three pieces connected: the session context (task, plan and conversation), the diff ready for review, and the same isolated working tree. Because the conversation is preserved, a prompt such as asking Copilot to add a test for "the updated label" still has the context to interpret it.

The rest of the walkthrough is deliberately ordinary engineering hygiene: review the diff in the Source Control view, check conventions and edge cases, run commands like npm test and npm run lint in the integrated terminal, and verify UI states at different viewport sizes. GitHub's stated division of labor is that Copilot takes on larger or repetitive implementation while the developer moves into the editor for review, targeted edits, local testing and final polish.