[BUG] Claude Desktop plugin browser shows repository name as author and marketplace source, ignoring metadata

What's Wrong?

In the redesigned Claude Desktop plugin browser (Settings → Plugins → Browse), the source filter and the author/byline both display the GitHub repository basename instead of the configured marketplace name and plugin author.

This is specifically the Claude Desktop settings UI, not the terminal /plugin picker. If this repository is not the right tracker for this shared plugin UI, please route the report to the appropriate team.

For our marketplace:

• Repository originally: anjsolution/plugins
• .claude-plugin/marketplace.json: name: "anjsolution", owner.name: "Ai-Ops"
• Each plugin's .claude-plugin/plugin.json: author.name: "Ai-Ops"
• Actual source filter: plugins
• Actual Korean byline: plugins 작성 (approximately "by plugins")

The organization identity is lost, and a repository name is presented as the author.

What Should Happen?

• Use the configured marketplace name, or an explicit marketplace display name, for the source label.
• Use the configured plugin author for a label presented as an author/byline.
• If the intent is to show the source instead of the author, label it as a source rather than "by" / "작성".

Steps to Reproduce

1. Create a GitHub repository named plugins, with this marketplace manifest:

{
  "name": "example-company",
  "owner": { "name": "Example Team" },
  "plugins": [
    {
      "name": "example-tool",
      "source": "./plugins/example-tool",
      "description": "Example tool",
      "version": "1.0.0",
      "author": { "name": "Example Team" }
    }
  ]
}

1. In plugins/example-tool/.claude-plugin/plugin.json, set:

{
  "name": "example-tool",
  "description": "Example tool",
  "version": "1.0.0",
  "author": { "name": "Example Team" }
}

1. Include a valid skill under that plugin and add the repository as a marketplace in Claude Desktop.
2. Open Settings → Plugins → Browse, and inspect a plugin byline and Filter → Source.
3. Compare the displayed source/byline with the repository name, marketplace name, and author.name.

The JSON above is an anonymized minimal example of the configuration we tested.

Observed Comparisons

| Configuration / source | Observed byline | Observed source filter |
| --- | --- | --- |
| Our repository named plugins, marketplace name anjsolution, owner/author Ai-Ops | plugins 작성 | plugins |
| obra/superpowers-marketplace, marketplace owner Jesse Vincent | superpowers-marketplace 작성 | superpowers-marketplace |
| After changing our repository name to anjsolution-marketplace | anjsolution-marketplace 작성 | anjsolution-marketplace |

We also tried explicitly adding author: {"name": "Ai-Ops"} to every marketplace plugin entry, alongside the existing plugin-level author, and bumping plugin versions. This did not change the source or byline. Adding displayName did update the individual plugin titles, confirming that at least those updated metadata fields reached the UI. That metadata experiment was subsequently reverted.

These observations suggest that the UI derives this source/byline from the repository basename. This is an inference from the UI comparisons, not a claim about the internal implementation. Whether an existing marketplace registration always updates automatically after a repository rename has not been established.

Is this a regression?

Yes, based on the user's prior experience: before the recent plugin UI change, the marketplace appeared as anjsolution and the author as Ai-Ops. The exact last-working app version and first affected version are unknown.

Environment

• Claude Desktop for Windows: 1.52386.0 (read from the running executable's ProductVersion/FileVersion)
• UI language: Korean
• Affected surface: Settings → Plugins → Browse, plugin detail byline, and Filter → Source
• Claude Code CLI version: not captured; this reproduction is in the Desktop settings UI
• Model/API platform: not applicable to this metadata display issue
• No error message or stack trace; this is a UI metadata/attribution issue

The observations above were checked against screenshots, but image files are not attached to this report.