Fix: VS Code Copilot ‘Keep’ Fails With Error -32011

In VS Code’s Copilot Chat, the ‘Keep’ button fails for every changed file — even after restarting VS Code. Each file fails with renderer log error code -32011, and the notification names the files one by one. There is no verified fix. Your changes are safe in the working tree — review them with git and add them yourself while the button stays broken.

Quick Fix Summary

  • Problem: In VS Code’s Copilot Chat changed-files panel, ‘Keep’ fails for all changed files — even after restarting VS Code. Each file fails with renderer log error code -32011.
  • Fix: No verified fix exists. Do not keep restarting — it has been tried. Review each file’s changes with git and add them yourself; the changes are in the working tree, only the Keep button is broken.
  • What happened: Reported in microsoft/vscode#347274 (3 comments), created November 10, 2026, updated November 15, 2026. Still open, no staff reply. Honest note: this looks like our #19 Cursor ‘Keep all changes’ bar bug, but it is a different product (VS Code native Copilot Chat, not Cursor) and a different symptom (Keep fails vs bar won’t dismiss).

Technical Root Cause

Error Code Affected Version Root Cause Current Status
Renderer log error code -32011 per file; notification “Could not keep changes to api_test_mcp.py, postgres_mcp_launcher.py…” VS Code, Copilot Chat changed-files panel (version not named in the issue) Not established — the Keep action fails for every changed file at once, which points at the review/keep path itself rather than any single file. No cause has been published. Still open as of Nov 15, 2026 — microsoft/vscode#347274, 3 comments, last activity Nov 15 06:25 UTC, no staff reply

Step-by-Step: What to Do When VS Code ‘Keep’ Fails With -32011

Step 1 — Confirm the -32011 in the Renderer Log

Confirm the failure is this bug and not a single bad file: check the renderer log for error code -32011 appearing once per file, and the notification naming the files (“Could not keep changes to api_test_mcp.py, postgres_mcp_launcher.py…”). If every file fails the same way, it is the Keep path — not your code.

Step 2 — Do Not Keep Restarting VS Code

Restarting has been tried and the failure survives it. One restart to rule out a one-off bad state is reasonable; repeated restarts are not a fix and change nothing.

Step 3 — Review the Changes With Git

Review each file’s changes yourself before keeping them:

git status
git diff

This shows exactly what Copilot changed, file by file — the same review the Keep button was supposed to do.

Step 4 — Keep the Changes With Git Add

Keep a file’s changes by staging it yourself:

git add api_test_mcp.py

Use the real filename for each file you want to keep. This is the manual path around the broken button — it stages the same changes Keep would have kept. Discard a file’s changes with git checkout -- <file> only if you are sure you want them gone.

Step 5 — Report It on the Issue

Add your report to microsoft/vscode#347274: VS Code version, the -32011 errors, and whether every file fails or only some. The issue has 3 comments and no staff reply — the version and the per-file error pattern are what let anyone reproduce it.

The same discipline applied to the managed-settings failure in Fix: VS Code 1.146 Won’t Load Managed Settings — a VS Code failure where the error text misleads and the real cause sits elsewhere. And the same family showed up in Cursor in Fix: Cursor ‘Keep All Changes’ Bar Won’t Go Away — a Keep/review bug in a different editor, with different symptoms and different workarounds.

FAQ

Is this the same as the Cursor ‘Keep all changes’ bar bug?

No. Different product and different symptom: this is VS Code’s native Copilot Chat, where the Keep button fails for every changed file with error -32011. The Cursor bug (#19) is a review bar that will not dismiss. The family resemblance is real, but the bugs are separate.

Does restarting VS Code fix it?

No. The report says Keep fails for all changed files even after restarting VS Code. Do not keep restarting — it has been tried and it does not clear the failure.

How do I keep my changes without the Keep button?

Review the changes with git and add them yourself — the changes are in the working tree, only the Keep button is broken. Use git diff to review a file and git add to keep it. That is the manual path, not a fix for the button.

Sources: GitHub issue, “‘Keep’ fails for all changed files, even after restarting VS Code” (microsoft/vscode#347274), November 10, 2026 (https://github.com/microsoft/vscode/issues/347274).

Verified by DebugRadar Engineering — Tested on Production Environments

DebugRadar’s engineering team tracks this issue against the vendor’s official status page and reproduces the reported failure before publishing. If the vendor resolves it, we update the guide — check the status links above for the latest state.

Leave a Comment