Plugins issues on VS Code
Issues the maintainers labelled both platform:vscode and area:plugins.
63 issues · 17 open · 46 resolved (73%) · first seen Feb 25, 2026
Is this getting better or worse?
This class of problem is holding steady. 21 new reports in the last 90 days vs 26 in the 90 before — -19%. The open backlog peaked at 17 in 2026-10 and sits at 17 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
49 of these reports name the Claude Code build they were running, spanning 39 releases. Heaviest reporters:
- Claude Code v2.1.289
- Claude Code v2.1.161
- Claude Code v2.1.296
- Claude Code v2.1.287
- Claude Code v2.1.241
- Claude Code v2.1.179
- Claude Code v2.1.200
- Claude Code v2.1.78
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 46 closures. Of the 46 closures with a recorded reason, 22% were closed as completed and 36 as not-planned or duplicate. The most recent completed fix landed in 2026-09.
Workarounds reported by the community
25 of these issues post a workaround someone says worked. The highest-engagement ones:
- [BUG] Local-scoped plugin fails to load on Windows with `plugin-cache-miss` due to case-sensitive `projectPath` comparison
- …nstalled and valid, while the VS Code extension reports . - Workaround confirmed: editing to change the drive letter to match the extension's launch case resolves the issue until the next install/update/enable operation.…
Found in the description of #74912 · still open - [BUG] Plugin management is broken in several connected ways (scope flag, UI writes to wrong scope, silent load failures, duplicate entries)
- …manually added install records for both projects (the only workaround for Bug 3), the Manage Plugins UI started showing the same plugin twice — one row per install record, with no label indicating which row belongs to w…
Found in the description of #70655 · resolved - [BUG] Project-scoped plugin installs (--scope project) load in CLI sessions but are silently ignored by the VS Code extension
- ….1.181 (Note: There was not a published 2.1.180) 3. A quick workaround is to manually edit and and replace upper case drive letters with lower case drive letters (e.g. replace with ) and restart VSCode. Then run to see t…
Found in the thread of #74612 · resolved - VS Code extension: "Skill must provide a name" warning is incorrect for plugin-namespaced skills
- …rkspace authors can override validation behavior themselves Workaround Attempted Added with — but this setting name is a guess, as no suppression setting is documented. Environment - Claude Code VS Code extension (latest…
Found in the description of #42782 · resolved - [BUG] Plugins fail to load after VSCode restart on Windows — marketplace directory wiped on each startup
- …y is gone 6. Check — multiple directories with valid clones Workaround Run before each session: Environment - Claude Code : 2.1.78 - Platform : Windows 10 Pro (10.0.19045) - Shell : Git Bash (MINGW64) - Node : v22.22.0 -…
Found in the description of #35924 · resolved
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–63
Ranked by community engagement (reactions weighted over comments).
- [BUG] VS Code extension never draws mod UI (Pane, AbovePrompt, status, toast) although the engine accepts the vscode surface
- [FEATURE] VS Code extension: draw function-hook mod UI (AbovePrompt band, Pane)
- [Bug] Plugin skills prompted for Read permission on their own plugin directory files
- [BUG] Local-scoped plugin fails to load on Windows with `plugin-cache-miss` due to case-sensitive `projectPath` comparison
- Linear MCP plugin: create_issue tool advertised but returns 'Tool not found'
- [BUG] Plugin management is broken in several connected ways (scope flag, UI writes to wrong scope, silent load failures, duplicate entries)
- Telegram channel plugin: MCP connection silently drops, zombie processes pile up
- [BUG] Project-scoped plugin installs (--scope project) load in CLI sessions but are silently ignored by the VS Code extension
- [BUG] claude plugin list --json --available truncates stdout at 65536 bytes when piped (process.exit before pipe drains)
- VS Code extension: "Skill must provide a name" warning is incorrect for plugin-namespaced skills
- [FEATURE] Add ability to update plugins in VS Code extension's Manage Plugins pop-up
- [BUG] VS Code "Manage Plugins" shows "No plugins available" after adding second marketplace (e.g. anthropic-agent-skills)
- [FEATURE] Plugin UI API: add text direction (dir / textAlign) to Box, Text and Markdown so mods can render RTL (Hebrew/Arabic)
- VS Code extension: mods (plugin UI hooks) do not draw status line / toast / panes
- [Bug] Security-guidance plugin bypasses subscription billing and uses expensive model without warning
- [BUG] Plugins fail to load after VSCode restart on Windows — marketplace directory wiped on each startup
- [BUG] VS Code: plugin MCP server silently dropped when a claude.ai connector has the same URL (CLI keeps the plugin)
- VS Code extension: SessionStart plugin hook additionalContext logged as succeeded but never injected into model context
- [BUG] claude plugins --json fails with "unknown option '--json'" in Manage Plugins panel (v2.1.145)
- Third-party marketplace plugins cannot register skills/commands/agents
- [BUG] Session permanently bricked: 400 "Tool reference 'LSP' not found in available tools" after a deferred tool leaves the pool mid-session
- [BUG] ralph-loop: Stop hook fails to detect a correct <promise> when the transcript window contains a control character
- Project-scope permission grant strips unknown top-level keys from .claude/settings.json
- [BUG] VS Code Chat panel Agent Handoff to Claude fails with "Error: Error during execution" (Windows, v2.1.145)
- VS Code extension silently drops a single plugin skill while siblings load correctly
- Plugin loader silently breaks when installed_plugins.json and known_marketplaces.json drift after marketplace refresh
- [BUG] bug: Claude Code plugins crash on Windows when user path contains accented characters
- VSCode extension: Plugin MCP tools not indexed in deferred tool search, causing misrouted tool calls
- [BUG] Plugins and MCP servers become invisible after alternating between Claude Code CLI and Antigravity IDE (VS Code extension)
- [BUG] Manage Plugins lists the same plugin once per install record, so two checkouts of one repo produce identical indistinguishable rows
- [Bug] Plugin skills shadow built-in commands when names collide
- [BUG] VS Code extension: namespaced /plugin:skill form is not recognized; skills whose name matches a built-in command are unreachable
- [BUG] duplicate for 69380 Plugin hooks.json does not register the MessageDisplay hook event (other events load fine)
- [Bug] Memory Plugin Not Functioning
- `claude plugin list --json` truncates stdout at 64 KB when piped and breaks VS Code plugin manager "available" list
- [Bug] GitHub plugin fails with missing environment variable error
- [Feature Request] Remove or deprecate non-functional plugins
- [BUG] VS Code Manage Plugins panel renders only Installed — available list & search missing in v2.1.161 (native binary returns 196 available)
- [BUG] Manage Plugins UI writes incorrect source format to known_marketplaces.json, causing Plugins tab to show empty
- Skill tool's forked execution describes plugin skills instead of running them; ignores `context` frontmatter field
- Manage Plugins modal (VSCode extension) renders one row per project-scope install, all labeled identically
- [Bug] `/plugin install` slash command ignores @marketplace qualifier for plugin resolution
- [BUG] Windows: Plugin marketplace path breaks when username contains spaces/accents (VS Code task context)
- [BUG] User-scope plugin MCP server cannot access project directory — no cwd or env var pointing to project root
- [BUG] Windows: marketplace refresh fails with 'git is not recognized' when VSCode default terminal is Git Bash
- [Bug] Plugin manifest validation error: Unrecognized keys "category" and "source"
- VS Code: skill autocomplete resolves wrong skill when typing exact name
- [Bug] Plugin updates fail silently and version visibility is poor
- [BUG] VS Code plugin manager never renders manifest.version for installed plugins, although the host already sends it
- [Bug] Claude Security Plugin Scan Results Not Processed Correctly
- [BUG] VS Code extension: namespaced /plugin:skill form shows “No matching commands” and cannot be submitted; skills whose name matches a built-in command are unreachable
- Feature request: plugin UI contribution point in the VS Code/Cursor extension (webview/panel)
- [BUG] Regression: VS Code "Manage Plugins" shows "No plugins available" with multiple marketplaces (64KB JSON truncation, previously fixed in 2.1.117 — refs #47237)
- [BUG] VS Code extension: mod Pane never draws, but $.ui.open resolves { isPlaced: true }
- [Feature] Keep hover (motion tracking) when CLAUDE_CODE_DISABLE_MOUSE_CLICKS=1, for plugin panes
- [BUG] VS Code extension never loads project-scope @skills-dir plugins; Manage Plugins shows them as (suppressed) and writes that placeholder into enabledPlugins
- [Feature Request] Built-in plugin missing from /plugin list and /usage cost tracking
- [BUG]
- [BUG] sparsePaths git marketplaces clone empty since 2.1.274 (GIT_NO_LAZY_FETCH=1 on a blob:none clone; git ≤2.34 exits 0) and silently replace healthy clones — 2.1.278 retry never fires
- [BUG] Windows: project-scope `.claude/skills` plugins are silently suppressed in the VS Code extension when workspace trust was accepted from a terminal with a different drive-letter case
- [BUG] Plugin-shipped output styles not registered in 2.1.246: force-for-plugin ignored and style unresolvable by name (repro of auto-closed #64914)
- Unexplained <claude-code-hint> lines injected into background Bash log output, referencing a nonexistent plugin, paired with an instruction to withhold this from the user
- [BUG] Plugin marketplace auto-update runs synchronously inside PreToolUse hook path, causing multi-minute session hangs under concurrent sessions (Windows)