Skip to main content
Watch: I Built an AI App Without Leaving Databricks

GitHub Copilot CLI error

Copilot CLI: Failed to resume session: Error: Session file is corrupted (line 7103...

Error message
Failed to resume session: Error: Session file is corrupted (line 7103: SyntaxError: Unexpected token '', ""... is not valid JSON)

Status: Fixed in releaseLast verified 1 documented fix3 sources

What it means

The saved session transcript could not be parsed, so --resume or /resume refused to load it.

Causes

  • A transcript damaged by an interruption such as power loss (#1864).
  • Release notes list several cases that also produced this error: sessions created before 1.0.6 (fixed 1.0.7), sessions with extension permission prompts (fixed 1.0.45), and events with non-URL strings in URL/URI fields (fixed 1.0.52).

How to fix it

  1. Fix 1.

    Upgrade. 1.0.66: "Recover corrupted session history on load". 1.0.86: "Resume sessions even when transcript files contain recoverable corruption". The Copilot CLI bot closed #1864 saying it "appears to be resolved as of GitHub Copilot CLI v1.0.88".

More Copilot CLI errors

All 12 Copilot CLI errors

FAQ

What does "Failed to resume session: Error: Session file is corrupted (line 7103..." mean in Copilot CLI?

The saved session transcript could not be parsed, so --resume or /resume refused to load it.

How do I fix "Failed to resume session: Error: Session file is corrupted (line 7103..."?

Upgrade. 1.0.66: "Recover corrupted session history on load". 1.0.86: "Resume sessions even when transcript files contain recoverable corruption". The Copilot CLI bot closed #1864 saying it "appears to be resolved as of GitHub Copilot CLI v1.0.88".

Is this Copilot CLI error fixed?

Status: Fixed in release. A release fixed this. The affected versions note says where the fix landed. Affected versions: Reported March 2026 (pre-1.0.7 and later). Recovery added in 1.0.66 and 1.0.86. Closed as resolved in 1.0.88.

Sources

Last verified against 3 sources: official docs, maintainer replies and release notes.

Newsletter

Fixes for the tools you use, weekly

One email per week. New coding agent releases, what broke, and how developers are working around it.