Answer: Add a top-level `renames` map to `marketplace.json` that maps each former name to its current name (or to `null` when the plugin is gone), so Claude Code migrates existing users instead of reporting the plugin as not found. Status: Confirmed Entry: tool/claude-code/admin-and-enterprise/rename-plugin-renames-map Revision: 2 Digest: sha256:d2738caadad94af8 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:05:03Z Last changed: 2026-11-20T12:23:10Z (history guidance: — → append-only history) Last verified: 2026-11-20T12:23:10Z Next check: 2026-11-21T12:23:10Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of mechanism | renames | [1] | 2026-11-20 example rename | formatter | [1] | 2026-11-20 example new name | code-formatter | [1] | 2026-11-20 removed entry value | null | [1] | 2026-11-20 validation command | claude plugin validate . | [1] | 2026-11-20 history guidance | append-only history | [1] | 2026-11-20 Sources: [1] Anthropic. "Host and maintain a marketplace". https://code.claude.com/docs/en/plugins/host-marketplace.md Role: primary. Accessed: 2026-11-20T12:23:10Z Quote: "add a top-level `renames` map to `marketplace.json`" (Supports: mechanism) Quote: "This marketplace renames `formatter` to `code-formatter`" (Supports: example rename) Quote: ""formatter": "code-formatter"" (Supports: example new name) Quote: "or to `null` when the plugin is gone" (Supports: removed entry value) Quote: "run `claude plugin validate .` after editing the map" (Supports: validation command) Quote: "Treat `renames` as append-only history." (Supports: history guidance) Published: 2026-11-20T03:18:19Z Snapshot SHA-256: 3171e4023e590b260ff641a0ef9c916c959f679761309dfc4e5fcaf663cb26eb (captured 2026-11-19T12:18:34Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T12:18:35Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:23:10Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:23:10Z Last attempt: 2026-11-20T12:23:10Z Notes and limitations: Extracted automatically from a single official source (section "Migrate users with a renames map"). Related: https://latestn.com/tool/claude-code/admin-and-enterprise/restrict-login-organization How do I restrict Claude Code login to my organization? https://latestn.com/tool/claude-code/admin-and-enterprise/restrict-parent-settings-locks How do I restrict parent settings for Claude Code using locks? https://latestn.com/tool/claude-code/admin-and-enterprise/restrict-plugin-marketplaces How do I restrict which plugin marketplaces users can install in Claude Code? https://latestn.com/tool/claude-code/admin-and-enterprise/private-marketplace-access How do I grant access to a private Claude Code plugin marketplace for users without a git-host account? https://latestn.com/tool/claude-code/admin-and-enterprise/process-wrapper-vs-shell-prefix How does CLAUDE_CODE_PROCESS_WRAPPER differ from CLAUDE_CODE_SHELL_PREFIX in Claude Code? https://latestn.com/tool/claude-code/admin-and-enterprise/provide-mcp-servers-managed-settings How do I provide MCP servers to every user through managed settings in Claude Code? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:23:10Z | changed | history guidance: — → append-only history | [1] 2026-11-20T12:23:10Z | changed | removed entry value: — → null | [1] 2026-11-20T12:23:10Z | changed | history policy: append-only → — | [1] 2026-11-20T12:23:10Z | changed | removed plugin value: null → — | [1] 2026-11-13T03:05:03Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/admin-and-enterprise/rename-plugin-renames-map/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/rename-plugin-renames-map POST: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/rename-plugin-renames-map with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/rename-plugin-renames-map?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I rename a plugin in a Claude Code marketplace without breaking existing installs? Revision 2, last verified 2026-11-20T12:23:10Z. https://latestn.com/tool/claude-code/admin-and-enterprise/rename-plugin-renames-map (accessed 2026-11-21T09:58:27Z). @misc{LatestN_tool_claude_code_admin_and_enterprise_rename_plugin_renames_map_r2, title = {How do I rename a plugin in a Claude Code marketplace without breaking existing installs?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/admin-and-enterprise/rename-plugin-renames-map}}, note = {Revision 2; digest sha256:d2738caadad94af8; last verified 2026-11-20T12:23:10Z; accessed 2026-11-21T09:58:27Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/admin-and-enterprise/rename-plugin-renames-map