Core CLI issues on VS Code — page 2
Issues the maintainers labelled both platform:vscode and area:core.
184 issues · 42 open · 142 resolved (77%) · first seen May 22, 2025
Is this getting better or worse?
This class of problem is converging. 52 new reports in the last 90 days vs 81 in the 90 before — -36%. The open backlog peaked at 45 in 2026-08 and sits at 42 today.
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
134 of these reports name the Claude Code build they were running, spanning 101 releases. Heaviest reporters:
- Claude Code v2.1.228
- Claude Code v2.1.197
- Claude Code v2.1.131
- Claude Code v2.1.112
- Claude Code v2.1.296
- Claude Code v2.1.283
- Claude Code v2.1.280
- Claude Code v2.1.118
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 35 days across 142 closures. Of the 142 closures with a recorded reason, 15% were closed as completed and 121 as not-planned or duplicate. The most recent completed fix landed in 2026-10.
Workarounds reported by the community
38 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 101–184
Ranked by community engagement (reactions weighted over comments).
- [Bug] Multiple screenshots trigger image limit error with poor UX for recovery
- [BUG] VSCode: Switching to a lighter model mid-session leaves session stuck — misleading error makes recovery non-obvious.
- [Bug] Compaction functionality not working
- Compaction integrity bugs: dangling logicalParentUuid + title resolver prefers lastPrompt over firstPrompt
- [BUG] CLI session not writing .jsonl file — invisible to VS Code extension
- [Bug] Plan Mode exit confirmation message inconsistent with actual mode state
- [BUG] Oversized image in conversation history permanently breaks all subsequent API calls
- [BUG] Calude Code (VSCode extension) not honoring .claudeignore file, and not catching that it should have, causing too much token consumption
- [BUG] [VSCode] Crash when auto-compact triggers during plan mode — ExitPlanMode tool filtered out after compact boundary
- [BUG] Session degrades silently after version update mid-session
- Windows: EEXIST crash on startup - mkdir fails on existing parent directory
- [BUG] Claude Code VS Code extension 2.1.296, Remote (vscode-server) on Linux, model claude-opus-5-5
- [Feature Request] Improve Gerrit stack workflow support and cross-session memory management
- Compaction summary generates fabricated adversarial content, including instructions to conceal actions from the user
- [BUG] Claude Code CLI native binary spins at ~100% CPU indefinitely on startup (VS Code Remote-SSH, Ubuntu 26.04)
- [Bug] Claude Code fails to follow claude.md instructions correctly
- [BUG] Claude-generated cron silently used a stale standalone CLI to resume an active VS Code session, repeatedly rebuilding ~760k-token cache
- [Bug] Context limit exceeded prevents prompting and model responses truncated
- Interrupting mid-turn silently drops already-completed work from active context, with no warning and confident denial on query
- Session becomes unreachable ("No conversation found") after git worktree remove deletes its own working directory
- [Bug] Anthropic API Error: Context Limit Exceeded - Compaction Fails with Usage Credits Required
- Intermittent 400 'surrogates not allowed' when context contains emoji (astral chars)
- [BUG] Autocompact Buffer takes
- [BUG] (Critical!) contamination by an unknown session simirlar to the report => [Bug] Context contamination after auto-compact with unrelated email draft of Tejo/Sado Basin #63137
- Claude Code crashes with "Query closed before response received" on Linux HPC cluster
- Plan mode session pinned to generated filename — can't redirect approval UI to a different plan file
- [BUG] Windows 11 / v2.1.142: JSON Parse error during init - Unexpected identifier "C" after bash-path detection (telemetry dropped)
- [BUG] Prompt is too long after compaction
- [Bug] False Positive Detection Error
- [BUG]
- [Bug] Claude model performance below expected parameters in session
- [Bug] Anthropic API Error: 400 Invalid Request after /branch with concurrent tool use
- [Bug] Claude enters infinite reasoning loop consuming excessive tokens
- Claude Code edits files while in Plan mode
- [BUG] Claude Opus 4.6 in VS Code Suddenly reverted to 200K context window (from 1M) across all chats around 5pm PST
- Session resume corrupts JSONL: file-history-snapshot messageId collides with message uuid
- [BUG] Claude Code Session Recording Failure & Massive Token Usage Surge
- Process exits with code 1 mid-session at ~59% context (not saturation)
- [BUG] VS Code Messages getting truncated
- [Bug] Conversation compaction causes context loss and performance degradation
- Prompt is too long
- [Critical] Runaway: agent could not be stopped by any in-product means; only closing the VS Code window with the X button stopped it
- [BUG] Resuming a session that is already running forks its transcript; the next resume silently drops one branch
- [BUG] advisor_20260301 tool type 400 hard-fails every turn in an affected session; model switch does not recover
- Stale/fabricated "skill invoked earlier in this session" system-reminder appears across unrelated sessions
- [Bug]: VS Code extension shows incomplete conversation history after "Tool permission stream closed" error — session chain forks to a stale tool_use branch
- Prompt too long
- Session transcript lost despite being well within default 30-day retention (VS Code extension)
- Foundry: Opus 5 / Fable 5 context window falls back to 200k instead of 1M (missing native_1m_3p in model catalog)
- [BUG] Transcript loader silently discards all but one conversation branch on resume, losing delivered assistant messages
- [BUG] Mid-turn task-summary classifier gets the user's ask hard-truncated at 300 chars with no marker, and renders its complaint about that as the on-screen activity line
- gitStatus context snapshot reports `Current branch: HEAD` for a repo on a normal branch (phantom detached HEAD)
- Compaction hangs/fails to recover session when session log is extremely large (~775MB, 190k lines)
- [BUG] `/goal` and `/goal clear` report "No goal set" after a met/failed verdict while the Stop hook stays armed
- [Bug] Previous session messages reinserted in current session with exposed internal tags
- [BUG] /context reports 222% of model limit with self-inconsistent breakdown, causing immediate "Prompt is too long" on a fresh session
- VS Code extension /model toggle intermittently corrupts settings.json (malformed JSON), silently dropping all permissions and hooks
- Assistant output leaked a `user`-prefixed line that got re-ingested as a user turn
- Fabricated user message with non-standard <system_warning><ctx_interruption> wrapper appeared in model context after Esc interruption; absent from session transcript
- [Bug] Rewinding to early conversation point causes context injection dump instead of assistant response
- Fabricated <system-reminder> content in subagent tool-call results, correlated with concurrent parent-thread Plan Mode
- Claude Code keeps auto-retrying indefinitely after hitting usage/token limit instead of stopping
- Assistant output stream contaminated with stray synthetic data + fake system-reminder tag (persisted in assistant JSONL line); same-day phantom user message
- Claude Code VS Code extension crashes with ACCESS_VIOLATION (exit 3221225477) on Windows ARM64 — regression between 2.1.197 and 2.1.202
- Phantom user message (never typed, absent from session jsonl) appeared in model context
- Plan mode: edits to plan file in IDE are ignored when approving from conversation
- [Bug] Rewind fails to show messages after manually stopping subagents
- [BUG] Oversized plan file makes a session unrecoverable: compaction yields postTokens > preTokens, and resume replays the stale copy
- [Bug] Autocompact thrashing due to context window refill within 3 turns
- [Feature Request] Improve codebase scanning accuracy and simplify technical explanations
- [BUG] Prompt cache expires during active session, causing massive token spikes on next prompt
- [Bug] Conversation restart requires excessive token reuse after API-forced session termination
- Legacy .claude/scheduled_tasks.json is loaded by the VS Code runtime, enabled: false is ignored, jobs fire as user prompts, and the file is rewritten on disk
- [BUG] Mid-turn task-summary classifier keeps the previous conversation's `latestAsk` across /clear (and image-bearing prompts never refresh it) — activity line describes a cleared conversation
- Forced re-login wipes ~/.claude transcripts; concurrent instance deletes a live session's task output files (Windows)
- settings.json is written with an unlocked, non-atomic read-modify-write: concurrent sessions tear it ("Settings file failed to parse") and silently drop each other's keys (2.1.258, with repro)
- [Bug] Resume flag incorrectly interprets system message as user input
- [BUG]Session retention cleanup deletes transcripts well before documented 30-day default (VS Code extension)
- [BUG] "an image in the conversation could not be processed and was removed" is NOT removed from the transcript - poisons the prompt cache, every later turn billed as cache-creation (~12x), drains a session in ~3 turns [root cause + fix identified]
- Auto-injected "Continue from where you left off." is parented to the stale last-prompt leaf, silently orphaning every message that follows
- [BUG] Stale extension process resolves parked permission requests hours later, re-parenting the session tip onto an abandoned branch — resume then hides the real conversation
- [BUG] Queued image prompts are re-serialized into the session transcript 16-23 times, inflating .jsonl by GBs
- Foreign third-party web-page content streamed into an in-flight assistant message (same requestId, +81s after reply ended)
- [BUG] Fabricated tool-call/tool-result blocks injected into conversation (VSCode extension)