GitHub Copilot Chat to Markdown Converter

This GitHub Copilot chat to Markdown converter turns Copilot Chat answers and exported VS Code sessions into clean Markdown. Paste a reply, or upload the JSON from Chat: Export Chat… to save each session as a .md file. Code blocks are kept, and vscode://file links become plain file paths.

  • Paste or upload exported chats
  • Stays on your device
Copy an answer from Copilot Chat in VS Code or on GitHub, or select it and press Ctrl+C (⌘+C on a Mac). VS Code file links become plain paths.

Markdown options
Math formulas
Web citations

How to convert GitHub Copilot Chat to Markdown

Saving a Copilot Chat answer as Markdown takes three steps, in VS Code or on GitHub.

  1. Copy from Copilot Chat

    Copy an answer from the Chat view in VS Code or from Copilot on github.com, or select it and press Ctrl+C (⌘+C on a Mac).

  2. Paste it into the converter

    Formatting becomes Markdown as you paste. File links that only open in VS Code become file names with their line number, in code style.

  3. Copy or download the Markdown

    Copy the result into an issue, a pull request or your notes, or download it as a .md file.

Example

This sample has 2 VS Code file links. The converter turns them into app.ts:12 and price.ts:3, which make sense anywhere, and keeps both code blocks with their language.

Convert a Copilot answer with VS Code links

GitHub Copilot chat to Markdown converter features

One tool for a single answer or many exported sessions, with the fixes copying out of VS Code needs.

  • vscode://

    Links that work anywhere

    File links become file.ts:12 paths you can read in an issue, a ticket or an email.

  • 2

    Paste or upload

    Convert one answer, or VS Code sessions saved with Chat: Export Chat….

  • ```

    Code kept as code

    Code blocks keep their language, so they’re highlighted on GitHub and in VS Code.

  • .md

    Files or one document

    Download sessions as separate .md files in a .zip, or together as one Markdown file.

How to export GitHub Copilot chat history from VS Code

VS Code saves a chat session as JSON with one command. That file converts here, and you can drop several at once.

  1. Open the session

    Open the chat you want to keep in the Chat view.

  2. Run Chat: Export Chat…

    Open the Command Palette with Ctrl+Shift+P (⇧⌘P on a Mac), run Chat: Export Chat… and choose where to save the JSON file.

  3. Drop it into the converter

    Choose Upload export and drop one or more exported .json files, or a .zip of them. They’re read in your browser, not uploaded.

  4. Download the Markdown

    Each session becomes a chat in the list. Download them as .md files in a .zip, or as one .md file.

What the converter turns into Markdown

Everything Copilot Chat shows in an answer has a Markdown equivalent. This is what you get for each part.

In Copilot ChatMarkdown you getGood to know
Headings## HeadingEvery level is kept, from # to ######.
Bulleted and numbered lists- item, 1. itemNested lists keep their indent. Checklists become - [x] and - [ ].
Code blocksA fenced block named with its language, such as tsBlank lines in the code are kept.
Inline code` formatPrice `Kept as inline code.
File references` app.ts:12 `In exported sessions, the file name; in copied text, the file and line.
Tables| Tool | Price | and a | --- | rowRight and centre alignment are kept, and a | inside a cell is escaped.
Links[text](https://…)Only web and email links are kept.
Tool runs and editsNothingMessages like “Reading file” and applied edits aren’t part of the answer text.
Who said what## You and ## GitHub CopilotAdded in every exported session.

Save a Copilot CLI session as Markdown

GitHub Copilot in the terminal can write Markdown itself. In an interactive session, type:

  • /share file to save the session as copilot-session-<id>.md in the current folder, or /share file notes.md to choose the path.
  • /share gist to save it as a secret gist on GitHub.com instead.

/export works the same as /share. Those files are Markdown already; paste one here only if you want to clean it up the same way as a chat answer.

What’s included when you convert an exported VS Code chat

The JSON from Chat: Export Chat… holds every prompt and response of the session, with each response stored as parts: text, file references, code edits and tool runs. The converter keeps what reads as the answer:

  • Your prompts and Copilot’s answers, under You and GitHub Copilot.
  • File references as file names in code style, where Copilot mentioned them in the text.
  • The model you used, such as gpt-4.1, and the session’s date, in the YAML front matter.

Tool runs, such as reading files or running a terminal command, and the edits Copilot applied to your files are left out. Your code changes are in your repository, not in the chat.

Save Copilot chats in Obsidian, Notion or GitHub

Markdown opens in almost any notes app, so a converted chat stays readable long after you stop using Copilot Chat.

  • Obsidian: download your chats as a .zip, unzip it into your vault and keep YAML front matter turned on. Each note then starts with its title, dates, model and conversation ID, which Obsidian shows as properties you can search.
  • Notion: use Notion’s import, choose Markdown and pick the .md files. Each file becomes a page.
  • GitHub and VS Code: the files use GitHub Flavored Markdown, with tables, task lists and fenced code, and math in $ form renders on GitHub.
  • Pull requests and issues: paste the Markdown into the description or a comment; code blocks and file paths display as they do in VS Code.

Exported files are named with the chat’s date and title, such as 2026-03-12 Trip ideas.md, so they sort by date.

GitHub Copilot chat to Markdown FAQ

How do I export GitHub Copilot chat history in VS Code?

Open the session in the Chat view, run Chat: Export Chat… from the Command Palette and save the JSON file. Drop it here to get Markdown.

Why are file links broken when I paste Copilot answers?

VS Code’s rich copy turns file references into vscode://file links, which only VS Code can open. Paste the answer here and they become plain file paths with line numbers.

What does chat.richTextCopy.enabled do?

It controls whether VS Code copies chat answers as formatted text. Turned off, you get plain Markdown, without the vscode:// links but also without formatting in apps that don’t read Markdown.

Can I convert several Copilot sessions at once?

Yes. Drop several exported .json files, or a .zip of them, and download them as separate .md files or as one file.

How do I save a Copilot CLI session as Markdown?

Type /share file in the session. Copilot CLI saves it as copilot-session-<id>.md in the current folder, or at a path you give.

Does the export include code changes Copilot made?

No. The exported chat lists the edits, but the converter leaves them out of the Markdown; the changes themselves are in your files.

Where does VS Code keep Copilot chat history?

In VS Code’s workspace storage, as files that change format between versions. Chat: Export Chat… is the reliable way to get a session out.

Is this for Microsoft Copilot too?

This page is for GitHub Copilot. For the Copilot app and copilot.microsoft.com, use the [Copilot to Markdown converter](tool:copilot-to-markdown-converter).

Are my chats uploaded or saved?

No. The converter runs in your browser. Pasted text and exported files are read on your device and never sent to our server.