How to Export a GitHub Copilot Chat
GitHub Copilot’s chat threads contain the kind of context that disappears at the worst time: the code review explanation that justified a change, the debugging session that found the race condition, the refactoring plan you’ll want next sprint. GitHub doesn’t give you an export button for any of it. This guide shows how to export a Copilot chat conversation to a real document — PDF, Markdown, or Word — plus one honest boundary: where the export works and where it doesn’t.
Where export works (and where it doesn’t)
An honest scope statement before you install anything:
- Works: Copilot conversations on github.com/copilot in your browser — the chat experience on GitHub’s site. The extension detects the page and adds an export button.
- Doesn’t work: the Copilot Chat panel inside VS Code or Visual Studio. IDE panels aren’t browser pages, so a browser extension can’t reach them. For IDE chats, screenshots or manual notes are still the only route.
- Also works: Microsoft Copilot (copilot.microsoft.com) in Edge or Chrome — see exporting Copilot chats in Edge for that workflow.
If your Copilot history lives in the IDE, nothing in this guide will reach it — better to know now than after configuring things.
Why keep Copilot chats at all
- Code review rationale — the "why" behind a suggested change outlives the PR description
- Debugging arcs — the working fix and the failed attempts that ruled things out
- Onboarding material — a new teammate reads how a problem was actually solved, not just the final diff
- Cross-tool context — paired with your Claude Code sessions and ChatGPT threads in one searchable local archive
Export a Copilot chat in three steps
Step 1 — Install the extension. Add the free XWX AI Chat Exporter from the Chrome Web Store. No account, no signup.
Open the chat and pick a format
Step 2 — Open the conversation on github.com/copilot. The extension detects it automatically.
Step 3 — Click the floating button and choose your format. Markdown for the repo or your notes (free, unlimited), PDF for sharing, Word for docs that get edited. Code blocks keep their syntax highlighting in every format.
Which format for which purpose
| Format | Best for | Cost |
|---|---|---|
| Markdown | Committing to the repo, Obsidian, grep-able archives | Free, unlimited |
| Sharing with non-developers, permanent records | Free daily quota | |
| Word (.docx) | Docs that get edited and commented | Free daily quota |
| JSON | Scripted processing, building your own tools | Free, unlimited |
For a searchable archive across Copilot, Claude, and ChatGPT threads, the XWX Backup desktop app batch-exports them all into one local vault with full-text search.
Frequently Asked Questions
Can I export GitHub Copilot chat conversations?+
Not natively — GitHub has no export button for Copilot chats. The free XWX extension adds one on github.com/copilot: open the conversation, click the floating button, and save it as PDF, Markdown, Word, or JSON.
Does this work for Copilot Chat in VS Code?+
No. The IDE chat panel isn’t a browser page, so a browser extension can’t read it. The export covers Copilot conversations on github.com/copilot in the browser.
Can I export my GitHub Copilot chat history in bulk?+
Yes. The XWX Backup desktop app includes GitHub Copilot in its batch export — one file per conversation into a local folder, with scheduled export available for keeping the archive current.
Is exporting Copilot chats free?+
Markdown, TXT, JSON, and clipboard exports are free with no limits. PDF and Word exports include a free daily quota.
Does exporting violate GitHub’s terms?+
The extension reads conversations from your own logged-in session at human pace — it’s the same data your browser already displays to you. Batch operations use conservative pacing with automatic back-off. That said, export is a copy, not a workaround for access control: only export what you’re authorized to keep.