GitHub Copilot diff missing from edits

Open
#320,334 1 comment 2 reactions 1 assignee View on GitHub

@hediet is already working on this.

Since Jun 7, 2026.

Assessment

This issue has not been assessed yet.

Description

Suddenly the edits to a document by Claude Opus 4.8 are not showing a diff correctly. The model edited sections throughout the document. However:

  • The entire document shows green, as if the document was blank before.
  • If I select "Toggle Diff Editor for Chats Edits", it shows entire green on the right, and a blank document on the left—again as if the document was blank before.
  • However if I look at the conversation and click on the "Edited [foo.md +37 -41]" notification in the middle of the response, the correct diff is shown!
  • Likewise if I go to the Source Control view on the left and double-click that file, again a correct diff is shown.

Thus I can see the diff of changes in the literal "things change" and "Git difference" windows, but in the actual "what this round modified" I cannot see the individual edits. The consequence is that this prevents me from accepting or rejecting each document edit individually.

Perhaps because there were edits dispersed throughout the documents, the change diff algorithm thought there was one big addition? But even that doesn't make sense, because in that case should have have shown the entire document in red as deleted. But it's showing an empty document as the previous state.

I don't know how to reproduce this, but I'll watch for patterns.

Version: 1.123.0 (user setup)
Commit: 6a44c352bd24569c417e530095901b649960f9f8
Date: 2026-06-03T11:29:03+02:00
Electron: 42.2.0
ElectronBuildId: 14159160
Chromium: 148.0.7778.97
Node.js: 24.15.0
V8: 14.8.178.14-electron.0
OS: Windows_NT x64 10.0.26200
Dominant language
TypeScript
Stars
193k
Forks
42.9k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode

All issues in microsoft/vscode

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.