How to export GitHub Copilot chat from VS Code

Open the session in VS Code, open the Command Palette and run Chat: Export Chat. Keep the downloaded JSON unchanged. To make a readable handover, import it locally, check the recovered prompts and responses against VS Code, then download Markdown with matching All platforms access.

Short answer

Step by step

Select the original session: Open the chat you want to keep. Check that the expected prompts, replies and any tool activity are visible. Avoid attaching private files when creating a harmless test session.
Export the JSON: Open the Command Palette with Ctrl+Shift+P on Windows or Cmd+Shift+P on Mac, then run Chat: Export Chat. Save the file unchanged and retain it separately from converted documents.
Compare before relying on it: Import the JSON in ChatExports. Check the list and sample first, then use All platforms access to compare the full transcript against VS Code. Verify the first and last messages, speaker order and code blocks.
Create the handover: Download Markdown for local project notes or Word for editing. Add your own repository, commit, reviewed decision and remaining-work context separately. Conversion does not inspect your repository.

Choose the right Copilot export

GitHub Copilot in VS Code is not the consumer Microsoft Copilot privacy-dashboard CSV. VS Code's official session documentation describes exporting chats from the editor. The GitHub Copilot exporter handles its requests and response-parts structure.

GitHub.com is another interface. GitHub's web-chat export announcement describes Manage chat, Export, and JSON or Markdown. A web JSON download is not automatically the same schema as a VS Code session. For a readable web copy, use GitHub's native Markdown option rather than assuming our VS Code JSON importer fits it.

What to compare against the original

| Check | What matters |

| --- | --- |

| First and last turn | Both are present, not just the final answer |

| Speaker order | Each question precedes its recorded response |

| Code | Identifiers, indentation and fenced blocks remain complete |

| Tools and context | Warnings identify structured data and unfetched file references |

| Dates | Missing source timestamps are not invented |

ChatExports keeps ordered text and retains unfamiliar structured response parts as JSON with warnings. It never downloads referenced workspace files. Hidden or system-initiated requests can differ from the visible transcript. This is a record of the session, not a backup of your repository or proof the generated code works.

A practical coding handover

Illustrative workflow: you asked Copilot to explain a retry bug and suggest a fix. Keep the prompts and answer as a transcript, then add your own verified commit identifier, test results and unresolved decisions to a separate handover note. Do not label AI-generated code as tested until you have run it in the real project.

Use Markdown for readable source-controlled notes. Use Word when you need to remove unnecessary details and add review comments. Keep the unchanged JSON too, so you can compare it later.

Pricing, privacy and testing limits

Import to inspect the list and short sample. Full conversations and downloads use the US$25 one-time All platforms plan; US$10 is ChatGPT only. Existing All platforms access covers GitHub Copilot. Conversation contents stay in your browser.

Our structure tests use synthetic data. A freshly exported, authenticated session still needs a local original-to-import comparison. Report warning text only with private details removed, never your export or code contents. Open your session or compare plans.

Frequently asked questions

Is Microsoft Copilot CSV the same file?

No. Consumer Microsoft Copilot activity uses a privacy-dashboard CSV. This guide covers VS Code GitHub Copilot chat JSON.

Can I export GitHub.com chat directly as Markdown?

GitHub documents JSON and Markdown export under Manage chat on the web. This is separate from the VS Code JSON structure; use the native Markdown option for a readable web copy.

Will attached repository files be downloaded?

No. Recorded context metadata can remain in the transcript, but workspace file references are never fetched.