Skip to content

Rich text copy from Copilot Chat converts file links to non-functional vscode:// URIs #312422

Description

@AdrienFelipe

Problem

When copying text from the Copilot Chat panel using rich text copy (default behavior), file references that the agent formats as workspace-relative markdown links (e.g., [src/file.ts](src/file.ts#L10)) get converted to vscode://file/... URIs in the clipboard HTML.

These vscode:// links don't work when pasted into:

  • Azure DevOps wikis/work items
  • Microsoft Teams
  • Outlook emails
  • Confluence/Notion/other documentation tools
  • Any context outside VS Code

Expected behavior

When rich-copying from Chat, file links should be converted to either:

  1. OS file paths (e.g., C:\src\project\src\file.ts) — universally understandable
  2. Workspace-relative paths as plain text (e.g., src/file.ts:10) — portable and readable
  3. Or at minimum, the vscode:// scheme should be a clickable protocol handler that actually opens the file when clicked from outside VS Code

Current workaround

Setting "chat.richTextCopy.enabled": false gives plain markdown, but loses all formatting (headers, bold, code blocks, tables).

Reproduction

  1. Open VS Code with Copilot Chat
  2. Ask Copilot a question that references files in your workspace (e.g., "explain this file")
  3. Copilot responds with clickable file links in the chat panel
  4. Select the response text and copy (Ctrl+C)
  5. Paste into any external tool (Teams, ADO, Outlook, Notion, etc.)
  6. File links appear as vscode://file/... URIs that don't resolve

Environment

  • VS Code: 1.99+
  • OS: Windows 11
  • Copilot Chat: built-in (GitHub Copilot extension)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions