Codex Plugin
Install OSuite into Codex app, CLI, and IDE with one managed plugin bundle for hooks, MCP, approvals, and replay.
Use this page when
Read this page when you want one OSuite package to govern Codex app, Codex CLI, and Codex IDE integrations.
What the plugin includes
- plugin manifest
- MCP configuration
- hook configuration
- pre-tool and post-tool governance hooks
- a bundled governed-runtime skill
Why this is the primary path
The repo-local hook guide still exists for advanced teams. The plugin is the default path because it removes the need to assemble hooks, MCP, and prompt behavior by hand.
Install outline
- Install the plugin into the local Codex plugin directory or team marketplace.
- Enable hooks and plugin hooks in Codex config.
- Bind the plugin to the correct OSuite workspace with a workspace API key.
- Trust the project so repo-local assets can load.
Security defaults
- enforce hook mode
- block on guard failure
- require signatures
- require a trusted project
What success looks like
The plugin is working when Codex actions appear in OSuite with the correct workspace, approval path, and replay link without manual assembly by the user.
Use the advanced lane when
Use Codex hooks instead when engineers need repo-owned hook files and direct control over the hook layer.
Next pages
Codex hooks
Advanced engineering path for repo-local Codex hooks and project config when you need direct ownership instead of the packaged Codex plugin.
Messages and protocols
Governed collaboration first, interoperability second: how OSuite positions messages, A2A-style exchange, and signed-request trust lanes.