Skip to content

chore(plugins): add Claude display name#487

Merged
wonderwhy-er merged 1 commit into
mainfrom
codex/add-claude-plugin-display-name
Jun 4, 2026
Merged

chore(plugins): add Claude display name#487
wonderwhy-er merged 1 commit into
mainfrom
codex/add-claude-plugin-display-name

Conversation

@edgarsskore

@edgarsskore edgarsskore commented Jun 1, 2026

Copy link
Copy Markdown
Collaborator

Adding CC plugin displayname for better visibility

Summary by CodeRabbit

  • Chores
    • Updated plugin configuration to include display name metadata for the Desktop Commander plugin.

@coderabbitai

coderabbitai Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

This PR adds the displayName field with value "Desktop Commander" to both the marketplace plugin registry and the local plugin configuration metadata, ensuring consistent display naming across plugin discovery surfaces.

Changes

Plugin Display Name Configuration

Layer / File(s) Summary
Add displayName to plugin metadata
.claude-plugin/marketplace.json, plugins/claude/.claude-plugin/plugin.json
Both plugin configuration files now include a displayName field set to "Desktop Commander" for consistent display naming in marketplace and direct plugin contexts.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • wonderwhy-er/DesktopCommanderMCP#457: Introduced the initial .claude-plugin/marketplace.json and plugins/claude/.claude-plugin/plugin.json manifest files that this PR now augments with the displayName field.

Suggested labels

size:L


🐰 A dash of metadata, a touch of name,
Two config files now look the same!
"Desktop Commander" shines so bright,
The plugin display is now just right!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding a displayName field to plugin configuration files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/add-claude-plugin-display-name

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.claude-plugin/marketplace.json:
- Line 14: Remove the unsupported "displayName" field from the
.claude-plugin/marketplace.json manifest: locate the "displayName": "Desktop
Commander" entry and delete that key/value pair so the JSON only uses supported
manifest fields (e.g., "name", "owner", "plugins" and other documented
optionals); ensure the JSON remains valid (comma positions adjusted) after
removal.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8593fdd0-c2cf-4931-8a50-a2a87e0c4937

📥 Commits

Reviewing files that changed from the base of the PR and between 9c44119 and 9b87781.

📒 Files selected for processing (2)
  • .claude-plugin/marketplace.json
  • plugins/claude/.claude-plugin/plugin.json

"plugins": [
{
"name": "desktop-commander",
"displayName": "Desktop Commander",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Search for schema definitions or documentation for Claude plugin marketplace.json format

# Look for schema files or documentation that define the marketplace.json structure
fd -e json -e md -e txt --exec rg -l "marketplace.*schema|claude.*plugin.*schema" {} \;

# Search for other examples of displayName usage in plugin configurations
rg -n "displayName" --type json -C 2

Repository: wonderwhy-er/DesktopCommanderMCP

Length of output: 58


🌐 Web query:

What is the official schema for Claude plugin marketplace.json file and does it support a displayName field?

💡 Result:

As of June 1, 2026, the official schema for the Claude plugin marketplace.json file does not support a displayName field [1][2]. The marketplace.json file, typically located at .claude-plugin/marketplace.json, is used to define a plugin marketplace for Claude Code [1][3]. According to official documentation, the required and supported fields are as follows: Required Fields: - name: A kebab-case identifier for the marketplace [1][2]. - owner: An object containing marketplace maintainer information (typically including a name) [1][2]. - plugins: An array listing the available plugins [1][2]. Optional Fields: - $schema: A URL for JSON Schema validation [1][2]. - description: A brief description of the marketplace [1][2]. - version: The version of the marketplace manifest [1][2]. - metadata.pluginRoot: A base directory path for relative plugin sources [1][2]. - allowCrossMarketplaceDependenciesOn: An array of other permitted marketplaces [1]. While there have been community requests to add a displayName field to marketplace.json to allow for more user-friendly naming, it has not been implemented as part of the official schema [4]. Developers currently rely on the name field, which is required to be in kebab-case and is used for installation commands [1][2]. Official JSON schemas for these manifest files are hosted at json.schemastore.org for validation purposes [2].

Citations:


Remove unsupported displayName from .claude-plugin/marketplace.json

  • Claude Code’s official marketplace.json manifest schema does not define a displayName field for marketplace/plugin entries (only fields like name, owner, plugins, plus other documented optionals). This means the displayName value ("Desktop Commander") will be ignored and may fail schema validation if strict checking is enabled.
  • Remove the "displayName": "Desktop Commander", entry at line 14 and rely on supported fields instead.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.claude-plugin/marketplace.json at line 14, Remove the unsupported
"displayName" field from the .claude-plugin/marketplace.json manifest: locate
the "displayName": "Desktop Commander" entry and delete that key/value pair so
the JSON only uses supported manifest fields (e.g., "name", "owner", "plugins"
and other documented optionals); ensure the JSON remains valid (comma positions
adjusted) after removal.

@wonderwhy-er wonderwhy-er merged commit 666a0e6 into main Jun 4, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants