GitHub Copilot app sessions can be picked up in VS Code

The tutorial is framed around a common handoff point: the agent has finished the bulk of a change, but the developer still wants to inspect one implementation detail, adjust a few lines by hand, and run the project locally before shipping. GitHub's answer is to move the whole session rather than the output—VS Code opens the same isolated worktree, displays the existing session in the Copilot sidebar, and keeps the diff ready for review.

The guide walks through reviewing changes line by line in the Source Control view, prompting Copilot in the sidebar to explain an implementation choice, editing files directly in the worktree, and running the project's normal validation commands such as npm install, npm test, npm run lint, and npm run dev. It treats agent-generated changes as it would code written by a person: run the relevant tests, inspect failures, and verify behavior, including loading, empty, and error states for a UI change.

Because the branch already tracks the work, committing and pushing from VS Code updates the pull request without copying files into another checkout. The stated result is a division of labor—Copilot takes on larger or repetitive implementation while the developer moves into the editor for detailed review, targeted changes, local testing, and final polish—without splitting the work itself.