Skip to content

feat(codex): repo marketplace so Codex users can install the plugin before the directory lists it - #8

Merged
okwasniewski merged 1 commit into
tester-army:mainfrom
lil-bsz:codex/repo-marketplace
Sep 21, 2026
Merged

okwasniewski merged 1 commit into
tester-army:mainfrom
lil-bsz:codex/repo-marketplace

Conversation

@lil-bsz

@lil-bsz lil-bsz commented Sep 21, 2026 •

Copy link
Copy Markdown
Member

Why

Codex users have no way to install the TesterArmy plugin until the OpenAI Plugins Directory lists it, and that submission (Linear GTM-82) still waits on Business verification, a reviewer account and app PR #2409. Codex also reads plugin catalogues from GitHub repos: .agents/plugins/marketplace.json at the repo root, added with codex plugin marketplace add owner/repo, and the ChatGPT desktop app shows the same file as a source in its Plugins tab. This is the Codex twin of the Claude Code marketplace this repo already is.

What changes

.agents/plugins/marketplace.json: one plugin, testerarmy, source ./ (the root already carries .codex-plugin/plugin.json and the portable plugin.json), category Developer Tools, sign-in on install. Marketplace name testerarmy-agent-skills, the same as the Claude marketplace, so the install command reads the same on both:

codex plugin marketplace add tester-army/cli
codex plugin add testerarmy@testerarmy-agent-skills

scripts/check-plugin-manifests.sh and validate-plugin.yml: the new file is parsed, must name the same plugin as plugin.json, point at ./, and share the Claude marketplace name. CI runs on PRs touching .agents/plugins/**.

README: the two Codex commands next to the Claude Code ones, plus the sign-in note.

Verification

Tested with codex-cli 0.153.4 on this branch:

  • codex plugin marketplace add <local checkout> and codex plugin marketplace add lil-bsz/cli --ref codex/repo-marketplace (GitHub source) both register the marketplace
  • codex plugin list shows testerarmy@testerarmy-agent-skills 1.0.0
  • codex plugin add testerarmy@testerarmy-agent-skills installs to ~/.codex/plugins/cache/testerarmy-agent-skills/testerarmy/1.0.0 and codex mcp list then shows testerarmy https://tester.army/mcp (not logged in until codex mcp login testerarmy)
  • codex plugin remove and marketplace remove clean up fully
  • consistency script passes, and fails when the marketplace names a different plugin (checked); actionlint clean

After merge

Nothing to configure. The two commands above work for anyone with Codex. When the directory listing goes live, the repo marketplace keeps working alongside it.

🤖 Generated with Claude Code

Review in cubic

…efore the directory lists it

Codex reads a plugin catalogue from .agents/plugins/marketplace.json in any
GitHub repo (`codex plugin marketplace add tester-army/cli`), and the
ChatGPT app shows the same file as a source in its Plugins tab. This gives
Codex users the one-command install Claude Code users already have through
.claude-plugin/marketplace.json, without waiting for the OpenAI Plugins
Directory review.

Tested with codex-cli 0.153.4: marketplace add, plugin list shows
testerarmy@testerarmy-agent-skills, plugin add installs 1.0.0 and registers
the hosted MCP server at https://tester.army/mcp, plugin remove cleans up.

- .agents/plugins/marketplace.json: one plugin, source ./ (the repo root
  carries .codex-plugin/plugin.json), category Developer Tools, sign-in on
  install; marketplace name matches the Claude one.
- scripts/check-plugin-manifests.sh + validate-plugin.yml: the new file is
  parsed and must name the same plugin, point at ./ and share the Claude
  marketplace name.
- README: Codex install commands next to the Claude Code ones.

Refs Linear GTM-82.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No issues found across 4 files

Re-trigger cubic

@okwasniewski
okwasniewski merged commit 39bb75a into tester-army:main Sep 21, 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