Skip to content

Add Codex support for qa plugin (dual-host, no MCP)#5

Open
ShawnPana wants to merge 1 commit into
mainfrom
add-codex-qa-plugin
Open

Add Codex support for qa plugin (dual-host, no MCP)#5
ShawnPana wants to merge 1 commit into
mainfrom
add-codex-qa-plugin

Conversation

@ShawnPana

@ShawnPana ShawnPana commented Jun 18, 2026

Copy link
Copy Markdown
Collaborator

What

Makes the existing qa plugin installable from Codex, alongside Claude Code — by adding a .codex-plugin/ manifest next to the existing .claude-plugin/ in the same dir. The skills/ directory is shared, so no skill content is duplicated.

qa/
├── .claude-plugin/plugin.json    # existing (Claude)
├── .codex-plugin/plugin.json     # new (Codex)
└── skills/qa/                     # SHARED
.agents/plugins/marketplace.json  # new (Codex catalog)

Claude reads .claude-plugin/, Codex reads .codex-plugin/, each ignores the other.

No MCP

This is the skills-based plugin that drives the browser-harness CLI — nothing to do with the hosted MCP. The only shared-file change is making the SKILL.md install line host-agnostic (claude plugin install … or codex plugin add …).

Validated with codex-cli 0.133.0

codex plugin marketplace add <repo>   # Added marketplace `browser-use`
codex plugin list                     # qa@browser-use  not installed
codex plugin add qa@browser-use       # Installed; shared skills/ + references/ land in cache

(Side note: Codex's marketplace authentication enum is ON_INSTALL | ON_USE only — qa needs neither, so the field is omitted.)

Install (once merged)

codex plugin marketplace add browser-use/plugins
codex plugin add qa@browser-use      # then /qa <url>

Follow-up

  • browser-harness is remote-sourced from its own repo, so its .codex-plugin/ manifest belongs there. qa needs the browser-harness CLI (host-independent uv/pip install) regardless.
  • If more hosts land (Grok, …), worth moving to a single-source generator instead of hand-written per-host manifests.

🤖 Generated with Claude Code


Summary by cubic

Enable installing the qa plugin from Codex alongside Claude Code by adding a .codex-plugin/ manifest and a Codex marketplace entry. Skills are shared with the existing .claude-plugin/, so nothing is duplicated.

  • New Features

    • Added qa/.codex-plugin/plugin.json and .agents/plugins/marketplace.json (registers qa under browser-use).
    • Hosts read their own manifests; shared skills/ directory; no MCP or auth required.
    • Updated qa/skills/qa/SKILL.md with host-agnostic install guidance.
  • Migration

    • Codex: run codex plugin marketplace add browser-use/plugins, then codex plugin add qa@browser-use.
    • Ensure the browser-harness CLI is installed (via your agent’s plugin or uv/pip per the skill docs).

Written for commit a09436f. Summary will update on new commits.

Review in cubic

Ports the existing skills-based qa plugin to Codex by adding a
.codex-plugin/ manifest alongside the existing .claude-plugin/ in the
same dir — the skills/ directory is shared, so there's no duplicated
skill content. Claude reads .claude-plugin/, Codex reads .codex-plugin/,
each ignores the other.

- qa/.codex-plugin/plugin.json — Codex manifest + interface metadata
- .agents/plugins/marketplace.json — Codex catalog (lists qa)
- qa/skills/qa/SKILL.md — install line made host-agnostic
  (claude plugin install … OR codex plugin add …)

No MCP involved. Validated with codex-cli 0.133.0: marketplace add ->
plugin list -> plugin add all succeed and the shared skill + references
land in the install cache.

Follow-up: browser-harness is remote-sourced from its own repo, so its
.codex-plugin/ manifest belongs there; qa needs the browser-harness CLI
(host-independent uv/pip install) regardless.

Co-Authored-By: Claude Opus 4.8 (1M context) <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 3 files

Re-trigger cubic

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.

1 participant