GitHub Copilot Sessions Can Move to VS Code With Context, Diffs, and Worktree Intact
A handoff path for human review, edits, and tests after agent work
Key takeaways
GitHub has documented a handoff from a Copilot app session to Visual Studio Code. The workflow keeps the session context, changed-file diff, and the same isolated worktree, so a developer does not need to rebuild the task history in a new chat. This article explains the prerequisites and provides a practical review sequence: open the session, inspect the diff, edit locally, run the relevant tests, and decide separately whether to push. The feature is useful when agent work needs human judgment or local tooling, but continuity is not proof that the generated changes are correct. Repository permission, the same GitHub account in both applications, and an existing session with changes are still required.
By ENHE AI · 2026-10-21 · AI-assisted drafting and editorial checks.
Direct answer: continue the same session, then validate the code yourself
Select Open in VS Code from a Copilot app session to continue the same task in the local editor. GitHub says the user does not need to summarize the history or copy it into a new chat first.
This reduces handoff cost; it does not prove correctness. The first action after opening should be to review the diff and task goal, not to push or deploy immediately.
What is preserved and what is required
VS Code opens the project with the worktree associated with the session and displays the existing conversation in the Copilot sidebar. The session context remains available, the changed files are ready for review, and VS Code opens the same isolated working tree used by the session.
Prerequisites include the same GitHub account in the Copilot app and VS Code, repository access, a session that has made changes, and a supported VS Code installation selected by the user.
Handoff checklist: four steps for local validation
- Open the target session in the Copilot app and read the task, plan, and latest status. Confirm that it is the intended repository and line of work.
- Select Open in VS Code. If multiple supported editors or installations appear, choose the one normally used for that project. Confirm that the sidebar session and workspace match.
- Review the diff file by file, focusing on input boundaries, permissions, error handling, and tests. Preserved context is not a reason to accept unfamiliar changes.
- Run the project’s relevant tests and checks. Decide whether to commit or push only after results match expectations. Push, release, and deployment remain separate authorization steps.
Who benefits and when not to use it
This is most useful when an agent has produced reviewable changes that need a local debugger, terminal, or human design judgment. A conversation with no code changes usually does not need this handoff.
Related ENHE AI pages explain the Copilot app, the boundaries between app, IDE, and CLI, and multi-repository work in Slack or Teams.
FAQ
Does opening VS Code push the code automatically?
No. Review, editing, testing, and pushing remain user actions, and pushing should be an explicit decision.
Why is Open in VS Code missing?
Check that both apps use the same GitHub account, repository access exists, the session has changes, and the editor installation is supported.
Related tools and reading
These pages match the account, workflow, policy, or risk boundary discussed above; choose only what supports the current task.
- What the GitHub Copilot app is
- Choosing Copilot app, IDE, or CLI
- Multi-repository work in Slack and Teams
Conclusion
Treat the feature as a bridge from an agent draft to human validation: review and test first, then decide whether to keep the changes.
Official or source-linked video
A related demonstration embedded in the official article; normal viewing link only, without verified inline playback or unverified video claims.
The page provides a normal external viewing link only. It does not claim inline playback, an independent hands-on test, or unverified timestamps.
Copilot app demonstration linked from the GitHub article
What this means for everyday users
This is most useful when an agent has produced reviewable changes that need a local debugger, terminal, or human design judgment. A conversation with no code changes usually does not need this handoff.
Related tutorials
Related reading
What Is a Desktop AI Agent App?
A desktop AI agent app is an AI application that runs on a user's computer and organizes work around task sessions, repositories, models, tools, and automations. The GitHub Copilot App release makes the term easier to understand because the app is positioned around agent-driven development rather than simple chat. For ordinary users, the important distinction is not whether the AI can answer questions. It is whether the AI can work inside a bounded session, connect to code, choose a model, run in parallel, and leave enough context for human review. That makes permission, account, and rollback planning part of the definition.
How to Choose Between GitHub Copilot App, IDE Extensions, and CLI Agents
The GitHub Copilot App release changes AI coding tool selection from a simple IDE-versus-CLI question into a workflow-surface question. A desktop app can be useful when users want parallel sessions, GitHub integration, task continuity, and agent-driven work from one place. IDE extensions remain strong for everyday editing, while CLI agents can fit terminal-first workflows and automation. For Chinese users and small teams, the practical checklist should begin with repository access, model source, Copilot plan, BYOK keys, human review, and rollback. The best tool is the one whose permissions and workflow boundaries match the task, team habits, security expectations, and review capacity.
GitHub in Slack and Teams Adds Multi-Repository Work in One Conversation
GitHub’s Slack and Teams integration can now work across multiple repositories within a single conversation. That is useful when a reported problem spans a frontend and backend, but it is a different event from the original launch of the chat integrations. This article explains the change and provides a scoped investigation request that a non-programmer project owner can give a technical collaborator. It describes what evidence to request before moving from analysis to code changes and how to distinguish an issue, a proposed pull request, a merge, and a deployment. No account-level availability test or automatic resolution is claimed, and the announcement is not treated as permission to change every repository.
From Chat Boxes to Personal AI Companions: AI Assistants Are Entering the Desktop Execution Era
AI assistants are moving from answering questions toward continuing real tasks. AI agents, MCP tool ecosystems, personal memory, and local workbenches are pushing this shift together. For users, the real value is not another chat box, but less repeated context setup and more continuity from thinking to doing.
Eleven Realtime v1 Mini and Max Launch: Choosing a Voice-Agent Path
ElevenLabs launched Eleven Realtime v1 Mini and v1 Max on October 20, 2026. Both speech-to-speech models support more than 90 languages and over 17,000 voices, but they target different tasks: Mini emphasizes lower-cost natural conversations, while Max is designed for support, lead qualification, and multi-step work. This article offers a selection and migration checklist instead of repeating benchmark claims. It explains how to compare both models on the same script, what OpenAI Realtime API compatibility means, why WebRTC integrations must move to WebSocket, and when ElevenAgents is the better starting point for channels, knowledge bases, guardrails, testing, and monitoring.
GitHub CLI Adds Expiring OAuth Tokens: Check Git, Scripts, and Extensions First
GitHub announced an opt-in public preview of expiring, automatically refreshing OAuth credentials for GitHub CLI on October 21, 2026, beginning with version 2.103.0. Users can enable the behavior with gh auth login --expiring or a global configuration setting. Git over HTTPS should use gh auth setup-git, and Git 2.46 or newer is recommended to avoid caching credentials beyond their lifetime. This article focuses on AI coding tools, scripts, and extensions that capture gh auth token output once and reuse it. It provides an inventory, migration, and verification sequence so users can gain a shorter exposure window without unexpectedly breaking long-running automation.