Skip to content

Add Codex plugin packaging for browser-harness#453

Closed
ShawnPana wants to merge 1 commit into
mainfrom
add-codex-plugin-manifest
Closed

Add Codex plugin packaging for browser-harness#453
ShawnPana wants to merge 1 commit into
mainfrom
add-codex-plugin-manifest

Conversation

@ShawnPana

@ShawnPana ShawnPana commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

What

Makes browser-harness installable from Codex — without touching the load-bearing root SKILL.md (which the Claude plugin and the global ~/browser-harness/SKILL.md import both use).

.agents/plugins/marketplace.json              # Codex catalog
codex/browser-harness/
├── .codex-plugin/plugin.json                 # Codex manifest
├── skills/browser/SKILL.md                   # COPY of root SKILL.md
└── README.md                                 # notes the copy + sync caveat

Why a copy

Codex requires a plugin to be a self-contained subdir with skills/<name>/SKILL.md (it copies the directory into its cache), so it can't point back at the repo-root SKILL.md the way the Claude plugin (which remote-sources the whole repo) does. The root file stays canonical; this is a copy. Root SKILL.md is unchanged.

Validated with codex-cli 0.133.0

codex plugin marketplace add <repo>   # Added marketplace `browser-harness`
codex plugin list                     # browser-harness@browser-harness  not installed
codex plugin add browser-harness@...  # Installed; skills/browser/SKILL.md lands in cache

Install (once merged)

codex plugin marketplace add browser-use/browser-harness
codex plugin add browser-harness@browser-harness

Still needs the browser-harness CLI (one-time uv/pip install) — the plugin ships the skill, the CLI is the tool it drives.

Follow-up

The skills/browser/SKILL.md copy can drift from the root. A small build step (generate the copy from root SKILL.md) removes that — worth doing once more hosts/plugins land.

🤖 Generated with Claude Code


Summary by cubic

Make browser-harness installable from Codex by adding a self-contained plugin under codex/browser-harness/, without changing the root SKILL.md. This enables marketplace installation and keeps the root skill as the canonical source.

  • New Features

    • Added Codex marketplace entry at .agents/plugins/marketplace.json.
    • Added plugin manifest at codex/browser-harness/.codex-plugin/plugin.json.
    • Added skills/browser/SKILL.md as a copy of the root skill to satisfy Codex’s self-contained plugin requirement.
    • Included codex/browser-harness/README.md with usage notes.
    • Verified with codex-cli 0.133.0.
  • Migration

    • Add marketplace: codex plugin marketplace add browser-use/browser-harness.
    • Install plugin: codex plugin add browser-harness@browser-harness.
    • Install the browser-harness CLI separately once (via uv/pip). The plugin ships only the skill.

Written for commit 8fcce35. Summary will update on new commits.

Review in cubic

Makes browser-harness installable from Codex without touching the
load-bearing root SKILL.md (which Claude + the global config import use).

Codex requires a plugin to be a self-contained subdir with
skills/<name>/SKILL.md (the dir is copied into Codex's cache), so it can't
reference the repo-root SKILL.md the way the Claude plugin does. This adds:

- .agents/plugins/marketplace.json — Codex catalog (its own marketplace)
- codex/browser-harness/.codex-plugin/plugin.json — Codex manifest
- codex/browser-harness/skills/browser/SKILL.md — COPY of the root skill
- codex/browser-harness/README.md — notes the copy + sync caveat

Validated with codex-cli 0.133.0: marketplace add -> plugin list ->
plugin add all succeed and the skill lands in the cache. Root SKILL.md is
unchanged. De-dupe (generate this copy from the root) is a later cleanup.

Install: `codex plugin marketplace add browser-use/browser-harness`
         `codex plugin add browser-harness@browser-harness`

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
Contributor

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

@ShawnPana

Copy link
Copy Markdown
Contributor Author

Closing — browser-harness is better treated as a CLI dependency than a standalone Codex plugin. The curated marketplace plugins (Linear, Cloudflare, etc.) avoid local installs by being hosted (remote MCP / OAuth); browser-harness needs a local CLI, and the Codex plugin form here was a thin copy of SKILL.md with dangling references to repo files (interaction-skills/, install.md) that don't get copied. qa already declares the browser-harness CLI as a prerequisite, which is the cleaner model. The real fix for install-free, cross-host use is a working hosted MCP.

@ShawnPana ShawnPana closed this Jun 18, 2026
@ShawnPana ShawnPana deleted the add-codex-plugin-manifest branch June 18, 2026 17:13
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