IDE integration issues on VS Code
Issues the maintainers labelled both platform:vscode and area:ide.
1,307 issues · 343 open · 964 resolved (74%) · first seen May 22, 2025
Is this getting better or worse?
This class of problem is converging. 519 new reports in the last 90 days vs 691 in the 90 before — -25%. The open backlog peaked at 343 in 2026-08 and sits at 343 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
732 of these reports name the Claude Code build they were running, spanning 161 releases. Heaviest reporters:
- Claude Code v2.1.63
- Claude Code v2.1.136
- Claude Code v2.1.129
- Claude Code v2.1.51
- Claude Code v2.1.170
- Claude Code v2.1.87
- Claude Code v2.1.198
- Claude Code v2.1.210
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 31 days across 964 closures. Of the 964 closures with a recorded reason, 21% were closed as completed and 758 as not-planned or duplicate. The most recent completed fix landed in 2026-08.
Workarounds reported by the community
380 of these issues post a workaround someone says worked. The highest-engagement ones:
- [FEATURE] VS Code Extension: Diff review UI similar to GitHub Copilot Edits Review
- …now. This breaks the developer flow completely. Relying on as a workaround is inconvenient and error-prone when dealing with large refactors. Really hope this gets prioritized!
Found in the thread of #33932 · still open - VSCode extension: add font size setting for chat panel
- …t, and there is no dedicated setting to change it. The only workaround is to zoom the entire VSCode window ( / ), which affects the whole IDE, not just the Claude panel. Proposed Solution Add a VSCode extension setting,…
Found in the description of #34196 · still open - [BUG] VS Code: "Not responding - try stopping" offers no way to actually stop or recover
- I am experiencing the same. Very annoying. Temporary workaround: when using the CLI and not the Vscode plugin, I have no issues.
Found in the thread of #39381 · resolved - [FEATURE] Show active model and thinking mode indicators in the VS Code extension panel
- <img width="371" height="517" alt="Image" src=" / In the meantime, Claude built me a usage meter for the macOS menu bar.
Found in the thread of #28986 · still open - [FEATURE] Multi-account support in VSCode extension
- …quota of a single Claude Pro account within a day. A common workaround is to maintain two separate Claude Pro accounts and switch between them. This works well in the terminal via , but the VSCode extension always uses a…
Found in the description of #55621 · 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). Listing the top 300 of 1,307 matches; the statistics above cover all 1,307.
- [FEATURE] VS Code Extension: Diff review UI similar to GitHub Copilot Edits Review
- Support /btw command in VS Code extension
- VSCode extension: add font size setting for chat panel
- [BUG] VS Code: "Not responding - try stopping" offers no way to actually stop or recover
- [FEATURE] Show active model and thinking mode indicators in the VS Code extension panel
- [FEATURE] Multi-account support in VSCode extension
- [FEATURE] VS Code Extension: Option to always show file diffs in VS Code editor panel instead of inline chat
- [FEATURE] VS Code Extension: Support queued message sending instead of interrupting current task
- VSCode extension: add option to prevent panel from stealing focus
- Support VS Code's browser-sharing API so Claude can validate web UI changes
- Add claudeCode.workingDirectory VS Code setting for multi-root workspaces
- [BUG] Remote control (/rc) not supported in VS Code extension
- Add batch diff review mode: show all changes together before approval (like Cursor's native agent)
- [BUG] First user message stays pinned/sticky at the top of the chat panel in VS Code extension
- [VSCode Extension] Add native system/toast notifications when Claude needs attention
- [BUG] VS Code extension ignores CLAUDE_CONFIG_DIR environment variable
- [FEATURE] VSCode extension: Copy chat response as markdown source
- [FEATURE] Syntax highlighting in VS Code extension chat panel (re-opening closed requests)
- Feature request: built-in completion notifications for VS Code extension
- Allow Claude to rename its own session (programmatic session rename API)
- [BUG] Past conversations not showing in dropdown - sessions-index.json not being updated.
- [BUG] Conversation history is lost in VSCode extension
- [BUG] Claude Code integration with VS Code not working on Windows
- [FEATURE] VSCode extension auto-includes opened files as context — should be opt-in by default
- [BUG] command 'claude-vscode.editor.openLast' not found
- VSCode extension: per-hunk accept/reject diff UI for file edits
- [BUG] VS Code extension doesn't load Chrome browser tools in chat panel despite docs stating @browser should work (Linux)
- Effort level 'max' should be persistable in settings.json for Max plan subscribers
- [BUG] Error installing VS Code extension: 1: ENOENT Please restart your IDE and try again.
- [FEATURE] VSCode extension: add a "Background Tasks" panel (parity with Desktop app)
- [VS Code Extension] v2.1.129 fails to activate on Windows: hardcoded Linux CI path in bundled SDK (regression)
- [FEATURE] Direct Read + Write feature for VS Code Virtual Workplaces like ABAP File system
- [BUG] `_claude_fs_right:/Users...` URL crashes rust-analyzer
- [Feature] Register Claude Code as VSCode Language Model provider to enable Agents window integration
- [FEATURE] Add --worktree support for parallel sessions in VS Code (same as Agent View in VSCode does)
- Extended thinking blocks not expandable for Sonnet/Opus/Fable in VSCode extension (works with Haiku)
- [BUG] "Fork Conversation from here" doesn't work
- [FEATURE] VS Code integrated browser support
- [BUG] Local session history disappears after VS Code restart
- [VSCode] Renaming session via sidebar pencil icon doesn't sync terminal tab title — next message overwrites the custom name
- Tabbed conversations in VS Code extension panel
- [BUG] Session titles revert to last-prompt text after session close, overriding custom-title entries
- [Feature Request] Add settings to disable auto-attaching active editor file and selection by default
- [FEATURE] Add /fork (conversation branching) support to VS Code extension
- VS Code extension: add a verbose toggle equivalent to CLI Ctrl+O
- [FEATURE] VSCode: Support adding multiple code selections to chat context incrementally via shortcut
- [BUG] Calling advisor tool crash or stop the claude code with following API error Unsupported content type: server_tool_use
- [BUG] no line numbers in VS Code plugin for modified files
- Expose /buddy companion in the VSCode native extension
- [FEATURE] Option to disable Up/Down arrow input history recall in VS Code extension
- [BUG] No conversation status displayed: regression in VSCode conversations list
- [BUG] command 'claude-vscode.editor.openLast' not found
- [BUG] Claude Code appears twice in VSCode sidebar after extension update
- VS Code: long user prompt cannot be collapsed (expand/collapse toggle unresponsive)
- VS Code extension: thinking blocks render without expand chevron
- [BUG] [VSCode Extension] Plan content not visible in panel before accepting plan mode prompt
- [BUG] Unable to view Claude's thinking process as of newest "claude code for VS code" version 2.1.141
- [BUG] v2.1.68 (updated 2026-03-04) opens 3 blank VS Code windows when claude is started in the integrated terminal.
- [BUG] Claude Code IDE connectivity issues with the latest update (1.0.64)
- [BUG] VS Code extension webview still renders 'Unsupported content type: server_tool_use' in v2.1.198 (prior reports #40816, #60446 auto-closed without fix)
- `showThinkingSummaries: true` silently no-ops on Opus 4.7 in non-interactive surfaces (VS Code extension, SDK, `--print`): one-line CLI fix or one-line extension fix
- [BUG] 2.1.198: chat code blocks have no container styling, so the host's default inline-code background leaks through as ragged per-line runs (stock VS Code)
- [FEATURE] Persistent config option to disable IDE context sharing (opened files, selections)
- [FEATURE] Support for Visual Studio Code "Next Edit Suggestions"
- [BUG] Session history empty in VSCode extension when working directory is on a mapped Windows drive
- Add option to keep plan mode inline instead of opening a new editor tab
- VS Code Extension: command 'claude-vscode.editor.openLast' not found when clicking Extension UI button
- [FEATURE] Inline editor diffs with line-by-line accept/reject (like Copilot)
- Starting Claude Code in VSCode integrated terminal opens 3 new VSCode windows
- VSCode extension: file links in chat panel look clickable but don't navigate or reveal the file
- [FEATURE] Add /fork (conversation branching) support to VS Code extension
- [VSCode] macOS Ctrl+F and Ctrl+P no longer work in chat input
- [BUG] VS Code extension ignores `remoteControlAtStartup` — re-filing after #41036 and #53647 were auto-misrouted by dup-bot
- [BUG] cursor <-> claude code integration does not work from inside tmux
- VS Code sidebar loses all session history after restart — sessions-index.json not updated for new sidebar sessions
- VS Code extension: text input types backwards (RTL direction bug) — frequent occurrence
- "Claude Code Extension Not Detected in VSCode Terminal"
- [BUG]macOS system shortcuts (Cmd+H, Cmd+M) not working when Claude panel is focused
- [BUG] Non-interactive system prompts are being injected into interactive sessions
- [BUG] Claude Code for VS Code API Error: 400 messages[1].role must be either 'user' or 'assistant', but got 'system'
- [BUG] Clicking thinking blocks no longer expands them in VSCode
- [BUG] [Windows] VS Code extension v2.1.129 fails to activate - hardcoded Linux CI path in extension.js
- [BUG] Extended thinking dropdown no longer expandable in VSCode extension (Opus 4.7)
- [BUG] AskUserQuestion dialog steals focus and captures keystrokes while user is typing in VS Code
- [BUG] mcp__ide__getDiagnostics available in CLI (integrated terminal) but missing from VSCode extension panel
- [FEATURE] Enable spellcheck in VSCode extension input (blocked on microsoft/vscode#214367)
- [BUG] Codicon font blocked by webview CSP font-src — diff markers render as tofu on 2.1.116 (extends #26836)
- [BUG] Copying text (Ctrl+C) from Claude Code window in VS Code fails
- [BUG] Windows absolute paths in markdown links: false affordance (renders clickable, click does nothing)
- [BUG] Horizontal scrollbar appears in panel mode due to missing horizontal padding in webview container
- [FEATURE] VS Code extension should honor remoteControlAtStartup (or expose claudeCode.remoteControlAtStartup)
- VS Code: New Claude Code tab ignores active editor group/column
- [BUG] Past Conversations empty on Windows with mapped network drives (realpath resolves to UNC path)
- /workflows slash command not recognized in VS Code extension
- [BUG] Plan-mode webview "Select text to add comments" — comments never reach the model
- [FEATURE] Render LaTeX math (KaTeX) in the VSCode extension chat panel
- [BUG] Claude COde doesn't work on WSL2, WHY ??????????
- [FEATURE] /workflows support in VSCode extension
- VS Code extension ignores sandbox settings.json / /sandbox unavailable (approval-fatigue fix unreachable in IDE)
- [FEATURE] [VSCode Extension] Allow independent font size configuration for Claude Code chat panel