Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[FEATURE] Show plugin version in the VS Code Manage Plugins dialog for installed plugins

Open Beginner friendly
  • Is something wrong?
#103,166 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, vscode
Domain
developer-experience, frontend

Research direction

Start in webview/index.js at the installed-plugin row rendering path described in the issue, and confirm that manifest.version already arrives through the list_plugins_response payload. Render that value beside or below manifest.name only when it is set. The change is done when installed plugins show their active versions in the Manage Plugins dialog, matching the requested presentation.

Written by the indexing model from the issue text.

Description

area:plugins enhancement platform:vscode
Preflight Checklist
  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)
Problem Statement

The VS Code extension's Manage Plugins dialog (opened via /plugins) lists every installed plugin by id only. No version is shown, so there is no way to tell from the UI which version of a plugin is actually active. The only way to find out is to leave the UI and run claude plugin list or read ~/.claude/plugins/installed_plugins.json.

This matters most for plugins vendored from upstream sources, where the marketplace and the upstream project version independently and the installed version is the only thing that identifies what is really loaded.

This is not a missing-data problem. The extension host already sends the version to the webview and the webview does not render it. In extension.js (2.1.301) the list_plugins_response payload for installed plugins contains:

manifest:{name:JQ($.id),version:$.version}

In webview/index.js the installed-row render path only reads manifest.name; manifest.version is not referenced anywhere in the webview bundle.

The CLI shows the value correctly:

$ claude plugin list
Installed plugins:

  > assembly-line@smoochy-marketplace
    Version: 0.5.0
    Scope: user
    Status: enabled

Previously reported as #89201 (closed automatically by the stale bot as inactive, not as fixed; the gap is unchanged in 2.1.301). Related but distinct: #78645 asks for the git ref to be surfaced and assumes the version is already displayed.

Proposed Solution

Render manifest.version on the installed plugin row when it is set, in the same way the Available section shows its metadata (description, install count, from <marketplace>). Next to the name (for example name v0.5.0) or as a second line under it would be enough.

The value is already in the props, so this is a rendering change in the webview, not a data-plumbing change.

Alternative Solutions

Current workarounds are claude plugin list in a terminal or reading ~/.claude/plugins/installed_plugins.json. Both require leaving the VS Code UI.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example
  1. Install a plugin from a marketplace that vendors an upstream project.
  2. Sync the marketplace.
  3. Open /plugins in VS Code to check which version is now active.
  4. Today every row shows only <name>@<marketplace>, so I have to switch to a terminal. With the version shown, I can confirm the update landed at a glance.
Additional Context

Environment:

  • Claude Code CLI: 2.1.302
  • VS Code extension: anthropic.claude-code 2.1.301 (win32-x64)
  • VS Code: 1.142.0
  • OS: Windows 11 Pro 10.0.26300
Dominant language
TypeScript
Stars
153k
Forks
26.7k
Avg merge
20h 45m
Merged PRs (30d)
21

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

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

More from anthropics/claude-code

All issues in anthropics/claude-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.