[JaweriaAsif]

Summary

• The next RELAI CLI release publishes this repo's Claude Code and Codex catalogs under the marketplace name relai, replacing relai-claude and relai-codex (REL-1152, relai-ai/relai-cli#789).
• Why: the CLI keeps the old names for the marketplaces it installs locally, and both hosts allow only one marketplace per name. Before, adding this marketplace repointed the CLI's Claude Code registration, and Codex refused the second add.
• relai-ai/relai-cli#789 recorded this README update as a release prerequisite. The release overlay doesn't include the README, so the publish job won't update it.

Behavior changes

• Install commands:
  • Claude Code: /plugin install relai@relai
  • Codex: codex plugin add relai@relai
  • The Cursor and Copilot sections are unchanged. The Cursor catalog keeps relai-cursor.
• Earlier installs: a new section, "Added this marketplace before it was renamed?", gives re-add steps for each host.
  • Claude Code: removing the marketplace also uninstalls relai@relai-claude.
  • Codex: removing the marketplace leaves relai@relai-codex installed and enabled, so the Codex steps start with codex plugin remove relai@relai-codex.
• One install per host: the "don't also run relai setup --agent" note now matches the CLI docs from #789:
  • also skip relai plugins install;
  • answer no to setup's plugin offer, including during first-run setup;
  • uninstall this copy before switching to the CLI's copy.

No generated files change.

Merge timing

Merge this right before, or together with, the next release PR: the first publish after relai-ai/relai-cli#789. The latest release here is v0.2.11 (#5).

• Until that release lands, the catalogs here are still named relai-claude and relai-codex, so relai@relai doesn't resolve yet.
• Once it lands, the old commands stop working.

Release PRs request auto-merge, so merge this as soon as the release PR is open.

Verification

• python3 scripts/validate_release.py --root . and python3 -m unittest discover -s tests pass.
• Simulated the migration with Claude Code 2.1.170 and Codex CLI 0.155.1, using isolated HOME, CLAUDE_CONFIG_DIR and CODEX_HOME and a local copy of this repo as the marketplace source:
  1. Installed relai@relai-claude and relai@relai-codex.
  2. Renamed both catalogs to relai, as the next release will.
  3. Ran this README's steps using the claude plugin … and codex plugin … CLI equivalents.
  • Each host ended with only relai@relai installed and enabled.
  • claude plugin marketplace update on its own kept the old relai-claude name.
• relai-ai/relai-cli#789 already checked, in isolated homes, that relai@relai installs alongside the CLI's own relai-claude and relai-codex copies without changing them.
• Not tested:
  • installing from GitHub with the renamed catalog, which exists only after the release;
  • the /plugin slash-command forms. I ran their CLI equivalents instead, as in docs: rewrite the README as a landing page #4.

🤖 Generated with Claude Code

[linear-code]

REL-1152 Give the public Claude plugin catalog its own marketplace name

Problem

The CLI's local plugin and the public catalog both use the Claude marketplace name relai-claude:

• Local: relai setup --agent claude and relai plugins install register extraKnownMarketplaces.relai-claude (pointing at ~/.relai/plugins/claude) and enabledPlugins["relai@relai-claude"] in ~/.claude/settings.json.
• Public: the relai-ai/coding-agent-plugins README tells users to run /plugin marketplace add relai-ai/coding-agent-plugins, then /plugin install relai@relai-claude.
• Both names come from CLAUDE_MARKETPLACE_NAME in src/agent_plugins/render.rs, which relai-plugin-export reuses.

Claude Code allows only one marketplace per name (marketplace reference). A user with both, for example someone who installs from the marketplace and later runs relai setup --agent claude, can have one refused or "added but ignored". It's then unclear which RELAI plugin is active. Codex (relai-codex) and Cursor (relai-cursor) also share names between the local and public catalogs; whether those hosts conflict the same way hasn't been checked.

Why now

coding-agent-plugins is still internal, so few users, if any, have added the public catalog. Renaming before it goes public (REL-1000) avoids migrating anyone. REL-1133's admin guide for allowlisting the marketplace (pluginSuggestionMarketplaces) will name it too.

Scope

• Choose the public catalog name. Proposal: relai, so users run /plugin install relai@relai.
• Give the public Claude catalog the new name in the export. Keep the local relai-claude as it is, because existing installs and relai uninstall depend on it.
• Check Codex and Cursor for the same conflict, and rename their public catalogs if they collide.
• Update the install commands in the coding-agent-plugins README and any docs that name the marketplace.
• Decide what a machine with both installs should do. With distinct names, both plugins load and every skill appears twice. Options: relai setup --agent claude detects an enabled marketplace copy and skips its own, or the docs tell users to pick one.

Done when

• ☐ The public catalogs' names don't collide with the CLI's local marketplaces, and the manifests pass claude plugin validate.
• ☐ The README and docs show the new install commands.
• ☐ The both-installed behavior is decided and covered by a test or the docs.

Related: REL-1133, REL-1000, REL-1150.

Review in Linear