Core CLI issues on VS Code

Issues the maintainers labelled both platform:vscode and area:core.

163 issues · 47 open · 116 resolved (71%) · first seen May 22, 2025

Is this getting better or worse?

This class of problem is converging. 65 new reports in the last 90 days vs 89 in the 90 before — -27%. The open backlog peaked at 47 in 2026-08 and sits at 47 today.

0 12 24 35 47 2025-052025-102026-032026-08
2025-05 — First reports2026-05 — Most new reports (34)2026-08 — Peak backlog (47 open)

Derived by counting each matching issue from its creation date until it closed. First-party computation over the anthropics/claude-code tracker — the trend is not published anywhere upstream.

Which builds report this

115 of these reports name the Claude Code build they were running, spanning 86 releases. Heaviest reporters:

Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.

Do these get fixed?

Median time to close is 33 days across 116 closures. Of the 116 closures with a recorded reason, 17% were closed as completed and 96 as not-planned or duplicate. The most recent completed fix landed in 2026-08.

Workarounds reported by the community

34 of these issues post a workaround someone says worked. The highest-engagement ones:

[BUG] VSCode ext - "Fork conversation from here" doesn't do anything
Yes, very appreciate if you can fix it. I mean you have AI on board :)
Found in the thread of #22016 · resolved
[BUG] Past conversations not showing in dropdown - sessions-index.json not being updated.
…sessions are indexed before they become visible to the user Workaround None currently available through the UI. Manual editing of is not recommended as it may cause other issues. Additional Notes - File permissions appea…
Found in the description of #18619 · still open
[BUG] `_claude_fs_right:/Users...` URL crashes rust-analyzer
…URIs will fail on this. Is there a timeline for a fix, or a workaround to prevent these notifications from being sent to LSP servers?
Found in the thread of #1522 · resolved
[BUG] Server-side experiment (`x-cc-atis`) silently removed Opus 4.8 thinking summaries, and the CLI silently self-updated even with `autoUpdates: false`. No notice, no opt-in, settings silently overridden.
…de gap, posted the analysis ( and built and shared a public workaround so other affected users could get summaries back: a launcher that injects , the one lever that is not interactivity-gated, plus an extension patch an…
Found in the description of #75607 · still open
Opus 4.8 returns empty thinking blocks — no thinking shown in chat (same regression as Opus 4.7 #49268)
…VS Code extension is unclickable / won't expand on Opus 4.7 Workaround Switch the session to or (both default to ) with . Request Have the Claude Code harness explicitly request for models that default to (Opus 4.7, Opus…
Found in the description of #63358 · still open

Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.

Matching issues 1–100

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. Core CLI issues on macOS

    3,395 issues
  2. Core CLI issues on Linux

    1,380 issues
  3. Core CLI issues on Windows

    1,285 issues
  4. Core CLI issues on WSL

    83 issues
  5. IDE integration issues on VS Code

    1,307 issues
  6. Model behaviour issues on VS Code

    463 issues
  7. Terminal UI issues on VS Code

    230 issues
  8. Cost and usage issues on VS Code

    203 issues