DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to change a published plugin's label without breaking installs with Claude Plugins Official

Update displayName or add a renames entry so existing users keep working.

Who it is forA marketplace maintainer who needs to change a published plugin's name or label.

The problemChanging the name field of a published plugin makes existing installs fail with a plugin-not-found error.

The outcomeThe plugin keeps working for current users, with its UI label updated or its old slug migrated to the new name.

What you need first

  • Claude Code with its plugin system
  • A plugin name listed in the claude-plugins-official marketplace
  • Git and a text editor for building or publishing a plugin

Steps

  1. Leave the name field unchanged, since it is an immutable slug for published plugins.
  2. To change the UI label, set or update displayName in the marketplace entry.
  3. If a rename is unavoidable, add an entry to the top-level renames map in .claude-plugin/marketplace.json, for example "old-name": "new-name".
  4. Verify that the old slug is mapped and the new name is correct before merging.

Prompt for your agent

In the anthropics/claude-plugins-official repo, update the marketplace entry for <plugin-name> so its UI label changes to <new-label> by setting displayName, without changing name. Output the diff. Verify that the name field is unchanged.

Caveat. The README says the Claude Code plugin loader rewrites old slugs on the user's next sync, but it does not say how long migration takes or what happens if a user is offline.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page