GitHub lets Copilot app sessions continue in VS Code
Developers can carry one Copilot task into the editor without starting over, keeping the same context as they review and change code.
GitHub says you can move an active Copilot app session into VS Code and keep the session, worktree, diff, and conversation context intact, which lets developers review, edit, test, and then push the same branch from the editor. The blog lays out the flow: open the session in VS Code, inspect the changed files in Source Control, continue the chat in the Copilot sidebar, make manual edits in the checked-out worktree, and run normal validation in the integrated terminal. It also says the app and editor stay linked through the original session so you do not have to recreate the task or copy files into another checkout. Separately, GitHub says its context-aware secret classifier improved detection quality, increased weighted acceptance by 11.5%, and cut median scan execution time by 86%.
Why it matters
That makes it easier to move from an AI-assisted task to hands-on editing without losing the thread of the work. Instead of restating the request or recreating the checkout, developers can inspect the branch, continue the conversation, and keep working in the same linked session and worktree.
Matters or hype?
Does this story matter, or is it hype? Vote before you see what everyone else said.
Sources
- GitHub Blog