Load Control Plane platform knowledge, guardrails, and live MCP access into Claude Code, Codex, and Gemini CLI — skills and agents that deploy workloads, troubleshoot failures, set up secret access, configure domains, and migrate from Kubernetes without hallucinating cpln commands.
Adding the marketplace does not install the plugin. Start Codex, open /plugins, use the arrow keys to navigate to Control Plane, then select and install the cpln plugin.
Update. Codex does not auto-update plugin marketplaces. Run the upgrade command when a new release is published, then restart Codex:
codex plugin marketplace upgrade controlplane
Enable plugin hooks for guardrail injection (recommended). Codex ships with the plugin_hooks feature off by default, which gates plugin-bundled hooks. The Control Plane plugin uses a SessionStart hook to inject the cli-conventions and cpln-guardrails rules into every Codex session so the assistant respects production write-guardrails (typed confirmations on destructive ops, org/GVC sanity checks, no invented cpln flags). To enable, add this block to ~/.codex/config.toml and restart Codex:
[features]plugins = trueplugin_hooks = true
After the restart, /plugins → Control Plane → Hooks should show SessionStart. Without this, Codex still loads skills and MCP tools, but the guardrails are not injected automatically and the Hooks row reads “No plugin hooks.”
Codex’s plugin format supports skills, MCP, and hooks (the latter behind the feature flag above). Agents and slash commands defined in the plugin are not loaded by Codex.
Install the extension from GitHub with auto-update enabled so future releases pull automatically:
The MCP server needs a service account token to act on your behalf. Skills, agents, commands, and guardrails work without it — the token is only required for live operations (creating workloads, managing secrets, applying manifests).
export CPLN_TOKEN="<your-service-account-token>"
Create a service account with the Create a Service Account guide. Add it to the superusers group for full access, or viewers for read-only exploration. Gemini CLI prompts for the token at install time and stores it in your system keychain.