claude-code — Claude Code plugin: what it does, how to install
A local MCP bridge connects Codex to an authenticated Claude Code CLI. Use it to check account status, sign in, or run workspace prompts in safe modes.
MIT ★ 1,596 updated 2026-10-29
/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install claude-code@awesome-codex-pluginsWhat claude-code does
This plugin links Codex with the Claude Code CLI installed on the same machine. Its MCP tools can inspect Claude Code and account readiness, open the official browser sign-in flow, and run workspace-scoped prompts with either manual or plan permissions.
The installer places the plugin in ~/plugins/claude-code, writes machine-specific MCP paths, and adds it to the Personal marketplace. Start a new Codex task after setup. The Node installer also supports update, uninstall, --destination-root <path>, and --force.
Claude Code keeps its own authentication state. The plugin never stores credentials, tokens, API keys, or account data, so authentication stays with the local CLI rather than a separate plugin store.
What it helps with
- check Claude Code installation and account readiness
- open the Claude Code browser sign-in flow
- review a repository in
planmode - request a second opinion on an implementation
- connect Codex to a local Claude Code CLI
Example prompts for the agent
- Check my Claude Code account status.
- Open the Claude Code sign-in flow in a browser.
- Run Claude Code in
planmode and review this repository.
How to install claude-code
Plugin marketplace
/plugin marketplace add hashgraph-online/awesome-codex-plugins/plugin install claude-code@awesome-codex-pluginsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about claude-code
How do I install claude-code in Claude Code?
Run these commands in order: /plugin marketplace add hashgraph-online/awesome-codex-plugins, then /plugin install claude-code@awesome-codex-plugins.
What does claude-code do?
It connects Codex to a local Claude Code CLI through MCP. The plugin exposes status checks, browser login, and workspace prompts with manual or plan permissions.
Does the plugin store Claude credentials?
No credentials, tokens, API keys, or account data are stored by the plugin. Claude Code remains responsible for its authentication state.
Source text
claude-code-codex-plugin · MIT
# Claude Code Plugin for OpenAI Codex A lightweight local bridge from Codex to the user's authenticated Claude Code CLI. The plugin has no runtime dependencies and never stores Claude credentials, tokens, API keys, or account data. ## Install From the repository root, run on Windows, macOS, or Linux: ```bash node plugins/claude-code/scripts/install.mjs install ``` Windows users can alternatively run: ```powershell powershell -ExecutionPolicy Bypass -File .\plugins\claude-code\install.ps1 ``` Use `update` or `uninstall` with the Node installer to perform those actions. The optional `--destination-root <path>` flag supports isolated test installations; `--force` explicitly replaces an existing installation. The installer copies the plugin to `~/plugins/claude-code`, writes machine-specific MCP paths, and adds the plugin to the Personal marketplace. Start a new Codex task after installation. ## Use | Tool | Purpose | | --- | --- | | `claude_code_status` | Check local Claude Code installation and account readiness | | `claude_code_login` | Open the official Claude Code browser sign-in flow | | `claude_code_prompt` | Run workspace-scoped prompts in safe mode with `manual` or `plan` permissions | Useful prompts: ```text Check my Claude Code account status. Open Claude Code login. Run Claude Code in plan mode and review this repository. Ask Claude Code for a second opinion about this implementation. ``` Claude Code owns its authentication state. This plugin only starts the local CLI and receives its normal command output.
© davidq888 · MIT · hashgraph-online/awesome-codex-plugins