Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Customize panel hides Version row when plugin version is in marketplace.json [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54279•Fetched 2026-04-29 06:31:35
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
nfrithnfrith
Participants
nfrithnfrith
Timeline (top)
labeled ×4

The Customize → <plugin> panel in Claude Code Desktop renders a "Version" row when the plugin's version field is in plugin.json. When the version is set in the marketplace.json plugin entry instead (a valid path per the version resolution waterfall), the Version row is omitted entirely from the panel.

Root Cause

The Customize → <plugin> panel in Claude Code Desktop renders a "Version" row when the plugin's version field is in plugin.json. When the version is set in the marketplace.json plugin entry instead (a valid path per the version resolution waterfall), the Version row is omitted entirely from the panel.

RAW_BUFFERClick to expand / collapse

Summary

The Customize → <plugin> panel in Claude Code Desktop renders a "Version" row when the plugin's version field is in plugin.json. When the version is set in the marketplace.json plugin entry instead (a valid path per the version resolution waterfall), the Version row is omitted entirely from the panel.

Reproduction

Case A — version in plugin.json:

  • plugin.json has "version": "0.1.1", marketplace.json plugin entry has no version
  • Customize → <plugin> shows: Version: 0.1.1 ✓

Case B — version in marketplace.json:

  • plugin.json has no version, marketplace.json plugin entry has "version": "0.1.0-beta.31"
  • Customize → <plugin> shows: no Version row at all

Expected

Version row renders in both cases. The resolution waterfall handles either configuration correctly server-side; the UI should match.

Actual

UX inconsistency between two documented-valid configurations.

Environment

Claude Code Desktop v2.1.121, macOS.

extent analysis

TL;DR

The issue can be fixed by ensuring the version resolution logic in the Claude Code Desktop UI correctly handles versions specified in both plugin.json and marketplace.json.

Guidance

  • Review the version resolution waterfall documentation to understand how versions are prioritized when specified in both plugin.json and marketplace.json.
  • Verify that the UI code correctly implements this logic to display the version row in the Customize → <plugin> panel.
  • Check for any conditional statements or filters in the UI code that might be causing the version row to be omitted when the version is set in marketplace.json.
  • Test the UI with different version configurations to ensure consistency in version row rendering.

Example

No code snippet is provided as the issue does not include specific code references.

Notes

The fix may require updates to the UI code to correctly handle version resolution and display the version row in all valid configuration cases.

Recommendation

Apply a workaround to ensure the version row is displayed consistently, such as always specifying the version in plugin.json until the UI issue is resolved.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#training loop#device allocation#model download#tokenizer error#prompt formatting

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING