Codex Plugin
Install devboy as a Codex plugin. Same architecture as the Claude Code plugin — agent-driven bootstrap, no bundled binary, MCP server registration, namespaced skills.
Install
Codex CLI reads the same Claude-style marketplace.json that the Claude Code plugin uses (one of the four marketplace sources documented in Codex plugin docs), so add this repo as a marketplace and install:
OpenAI's official Plugin Directory does not yet accept self-serve community submissions ("coming soon" per the official docs at the time of writing); the per-repo marketplace path above is the supported way to ship today.
What happens next
The bundled setup skill triggers on first use and:
- Detects plugin context —
$CODEX_PLUGIN_DATAis set, picks--agent codex. - Installs
devboy(npm → fallback to GitHub Release tarball in${CODEX_PLUGIN_DATA}/bin/, verified via the per-asset.sha256sibling; releases are not code-signed, the SHA file is the integrity check). - Runs
devboy onboard --agent codex --yes. - Runs
devboy doctor. - On failure, hands off to
repair.
After install, restart the Codex session so the MCP server entry binds against the new binary.
What the plugin ships
Skill names match the source one-to-one (no rename). Namespaced as /devboy:setup, /devboy:review-mr, …, /devboy:analyze-usage.
Compared to the Claude Code plugin
The two plugins share /crates/devboy-skills/skills/ as their source of truth and produce identical user-visible skill surface. Differences are mechanical:
devboy onboard dedups against ~/.codex/settings.json#enabledPlugins the same way it does for Claude.
Troubleshooting
Same playbook as Claude Code:
- After
setupfinishes, restart the Codex session for the MCP server to bind. - If
npm install -gfails, the GitHub Release fallback in${CODEX_PLUGIN_DATA}/bin/activates automatically. - For everything else, run
/devboy:repair.
See also
- ADR-018 — Distribution as Claude Code and Codex plugins
- Claude Code plugin install — sibling plugin, same architecture
- Codex Plugin Build Guide — upstream plugin spec