How to Continue a GitHub Copilot App Session in VS Code

GitHub Copilot has evolved from an inline code completion tool into a full-fledged AI pair programmer spanning multiple surfaces — the standalone Copilot app, the GitHub website, and popular IDEs like VS Code. As of 2026, developers increasingly switch between these environments throughout the day. A common question is: can you pick up a conversation started in the GitHub Copilot app and continue it inside VS Code? This guide explains the workflow.

Why Session Continuity Matters

Modern development workflows rarely happen in a single tool. You might sketch an idea in the Copilot app on your phone or desktop, then move to VS Code to write and test the actual code. Roughly, the goal is to avoid re-explaining context every time you switch environments. Session continuity helps you:

• Preserve conversation context across tools
• Reduce repetitive prompting
• Keep your AI-assisted work traceable and consistent

Prerequisites

Before you begin, confirm that you have:

1. The GitHub Copilot app installed and signed in with the same GitHub account you use in VS Code.
2. Visual Studio Code (current 2026 release) with the GitHub Copilot and GitHub Copilot Chat extensions installed.
3. A Copilot subscription that includes chat (individual, business, or enterprise plans all support this).
4. Your account signed in to GitHub inside VS Code via the Accounts menu.



Step-by-Step: Continuing Your Session in VS Code




1. Locate the conversation in the Copilot app




Open the GitHub Copilot app and navigate to the chat or conversation you want to continue. Copy the relevant context — prompt, generated snippets, or the full thread — or use the built-in share/export option if available in your version.




2. Open VS Code and launch Copilot Chat




In VS Code, open the Copilot Chat view (typically via the chat icon in the Activity Bar or the Command Palette: GitHub Copilot: Open Chat).




3. Paste or reference your context




Paste the copied conversation or key prompt into the chat input. For larger context, save the exported thread as a Markdown file in your workspace and reference it with #file in your prompt — for example:




Continue this implementation using the context in #file:copilot-session.md




4. Use workspace context to enrich the session




VS Code's Copilot Chat supports references to files, symbols, and the terminal. Connect the thread from the app to your project with references like #codebase, #terminalLastCommand, or specific files, so the assistant has the full picture.




5. Continue and iterate




From here, you can request code changes, ask for tests, or trigger agent mode to apply edits across multiple files — all while preserving the intent established in the original Copilot app session.




Tips for Smoother Handoffs



• Standardize on one GitHub account across the app and IDE to keep history consistent.
• Use Markdown exports for long conversations — they paste cleanly and are easy to reference with #file.
• Summarize before switching — a short recap prompt at the end of an app session often saves tokens and confusion later.
• Watch for sync features — GitHub continues to expand cross-surface session support in 2026, so check release notes for native handoff options.



Conclusion




While native one-click handoff between the Copilot app and VS Code continues to mature, you can reliably continue any session today by exporting or copying context and re-anchoring it to your workspace with file references. With a consistent account setup and a few good habits, switching between the Copilot app and VS Code becomes seamless — keeping your AI-assisted momentum intact from idea to implementation.

via GitHub AI Blog