[Copilot Sessions] Claude Code CLI sessions incorrectly marked as "Failed" after successful completion

Open

#319,043 opened on May 29, 2026 0 comments 0 reactions 1 assignee View on GitHub

@TylerLeonhardt is already working on this.

Since May 29, 2026.

Assessment

This issue has not been assessed yet.

Description

Does this issue occur when all extensions are disabled?: No
(Requires GitHub Copilot and Claude Code CLI extensions)

VS Code Version: 1.122.1
OS Version: Windows 10 Pro 10.0.19045
GitHub Copilot Extension Version: 0.50.1
Claude Code CLI Version: 2.1.112

Steps to Reproduce

Open a workspace in VS Code with GitHub Copilot and Claude Code CLI installed.
Start a new Claude Code session via the Copilot Sessions panel ("New" button).
Have a normal conversation with Claude Code — ask it to read files, answer questions, or write code.
Wait for Claude Code to complete its response (the CLI process exits normally).
Observe the session status in the Copilot Sessions panel.

Expected Behavior

Completed sessions should be marked as "Completed" (or similar) when the Claude Code CLI process exits with a successful status (stop_reason: end_turn).

Actual Behavior

All sessions are marked as "Failed" in the Copilot Sessions panel, regardless of whether the underlying Claude Code CLI process completed successfully. The chat UI also intermittently displays an "Error during execution" block when individual tool calls inside Claude Code fail and recover — this is normal recoverable behavior in Claude Code, but it is surfaced to the user as a top-level failure.

Root Cause (Investigated)

Inspecting the Claude Code session logs (~/.claude/projects/<workspace>/<sessionId>.jsonl), every session ends with:

{ "stop_reason": "end_turn" }

Dominant language: TypeScript
Stars: 193k
Forks: 42.9k
PR merge metrics: PR metrics pending

Contributor guide

Open the contributing guide

First steps

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

Similar issues

[Bug]: Session row status indicator sits flush against the selection pill's rounded corner Open

clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

openclaw/openclaw#154145 · 2 comments · 1 reaction · Opened Sep 20, 2026
[good first issue] 🀄 Add new Grammar Point 265 (good-first-issue) Open

community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs

Difficulty 1/5 Under an hour Newbie friendliness 76/100

lingdojo/kana-dojo#30632 · 1 comment · 5 reactions · Opened Sep 20, 2026
[Duplicate Code] Repeated filtered model-alias assembly in proxy server Open

code-quality refactoring

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

github/gh-aw-firewall#8816 · Opened Sep 20, 2026
quickjs: support `timeout=None` (no per-call deadline) in `CodeInterpreterMiddleware` Open

integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

langchain-ai/deepagents#6450 · Opened Sep 20, 2026
`QuotedTweet.self_thread` is optional in syndication responses Open

Difficulty 1/5 Under an hour Newbie friendliness 88/100

vercel/react-tweet#225 · Opened Sep 20, 2026

More TypeScript issues