TechFixSignal
GitHub Copilot

GitHub Copilot Request Failed 413 Failed to Parse

When Copilot Chat shows Request Failed 413 failed to parse request, stop retrying the same turn, run /compact or start a new chat, and cut image-heavy context.

Reviewed by TechFixSignal EditorialSee how this guide is verified

Last checked
Sep 22, 2026
Applies to
Windows, Mac, Desktop
Fix status
Community Confirmed
Fastest useful check

Quick answer

Match Sorry, your request failed. Please try again. with the reason Request Failed: 413 and failed to parse request. Do not spam Try Again on the same bricked turn. Run /compact if the model allows it, switch models briefly to compact then return, or start a new chat. Cut image-heavy or multi-view context, and keep VS Code on 1.116 or newer when images are involved. This is not a Refresh Authentication or Continue with undefined sign-in screen.

On this page

What we're seeing

  • The exact failure pairs Sorry, your request failed. Please try again. with Request Failed: 413 and a JSON body whose message is failed to parse request.
  • Independent March–April 2026 first-hand microsoft/vscode issues report the same 413 in Copilot Chat and editAgent turns when the session payload grew too large, including long GPT context and image-heavy prompts.
  • First-hand leftovers that cleared the brick include /compact, switching model briefly to finish compact, starting a new chat, and reducing images or multi-view attachments instead of retrying the same turn.
  • Try Again on the same turn often replays the oversized payload and keeps returning 413.
  • A VS Code 1.116 packaging fix addressed some image BASE64 paths; long-session GPT bricks still need compact or a new chat.

Start here

Try these first

Fix 1

Confirm Request Failed 413 failed to parse

Community Confirmed

Match the 413 parse fingerprint before clearing auth or reinstalling Copilot.

  1. Read the Copilot Chat error. This guide needs Request Failed: 413 with failed to parse request, not a bare Sorry, your request failed without 413.
  2. If the screen is Refresh Authentication, Continue with undefined, or Failed to sign in to undefined, stop here — those are different leftovers.
  3. Note whether the failing turn includes large prior chat history, many files, or images.

Applies to Windows, Mac, Desktop

Fix 2

Stop spamming Try Again on the same turn

Community Confirmed

First-hand reporters found Try Again kept replaying the oversized request that already failed with 413.

  1. Do not click Try Again repeatedly on the same failed response.
  2. Leave that bricked turn and prepare a compact or new-chat path instead.

Applies to Windows, Mac, Desktop

Fix 3

Run /compact or start a new chat

Community Confirmed

March–April 2026 first-hand vscode issues cleared long-context 413 bricks by compacting the conversation or abandoning the oversized session. If GPT blocks /compact, switch to another model briefly to compact, then return, or open a fresh chat.

  1. In Copilot Chat, run /compact if the command is available for your model.
  2. If compact is blocked on the current model, switch to another Copilot model, run compact or summarize, then switch back.
  3. If compact still fails, start a new chat and restate only the needed context.

Applies to Windows, Mac, Desktop

Fix 4

Cut image-heavy context and update VS Code

Community Confirmed

Image-heavy and multi-view turns were a repeated 413 path. VS Code 1.116 and later include packaging fixes for some image BASE64 cases. Prefer fewer images or a separate inspect step.

  1. Remove or reduce images and multi-view attachments from the next prompt.
  2. Check Help → About and update VS Code to 1.116 or newer when images are part of your workflow.
  3. Retry with a smaller prompt in a new or compacted chat.

Applies to Windows, Mac, Desktop

Device notes

Windows
Windows VS Code Copilot Chat and editAgent panels both surface Request Failed: 413 with failed to parse request.
Mac
macOS VS Code reports the same 413 parse string; prefer compact or new chat before clearing Copilot AppData.
Desktop
This guide is for the VS Code GitHub Copilot Chat UI, not github.com Copilot web alone.

Official information

Checked on 22 September 2026, first-hand microsoft/vscode issues document Sorry, your request failed with Request Failed: 413 and failed to parse request in Copilot Chat and editAgent. GitHub does not publish a single Help article that only names this 413 parse fingerprint. Some image packaging paths improved in VS Code 1.116; long-session compact or new-chat leftovers remain the try-today path.

Sources

Keep troubleshooting

Related problems