Bridge Claude with OpenAI Codex CLI for AI-to-AI collaboration, code review, and second opinions
Second opinions for coding agents.
Get a second opinion on your code or plan, inside your coding assistant, using the model subscriptions you already have.
For individual developers and small teams who already use a coding assistant and pay for another model subscription: ask a different vendor's model to review your changes or challenge your plan, without API keys, copy-paste, or leaving the session.
You: ask codex to review src/auth.ts for security issues
Codex: ⚠ verifyToken() compares tokens with === — not timing-safe (line 42)
⚠ the session cookie is missing a SameSite attribute
Claude: Good catches — applying both fixes to src/auth.ts.
You need Node.js 24+ on Linux or macOS. Before your first review, both your coding assistant (for example Claude Code) and the provider you will consult (for example Codex) must be installed and signed in. Ask LLM configures the connection; it does not install providers or sign you in. If a provider CLI such as Codex has never been signed in on this machine, sign in first and rerun setup.
npm i -g @ask-llm/mcp && ask-llm setup
Setup asks you to confirm each detected host and workflow. Inspect the preview, confirm your assistant's registration and workflows, decline the others, then follow any printed manual steps. Restart your assistant or start a new session in your project.
With both Claude Code and Codex installed and signed in, open Claude Code in your project and ask:
Ask Codex to review my staged changes for bugs and missing error handling. Check each finding against the source before proposing fixes.
Working in Codex with a Claude subscription? Ask Claude instead. Choose a provider from a different vendor than your current assistant. A successful review names the reviewer and model, cites relevant code, and reports findings or says it found none. Your assistant applies changes after you decide what to accept. If the request fails, run ask-llm doctor and follow the troubleshooting guide for your selected assistant and reviewer. Warnings about providers you do not use do not require installing them or adding API keys.
For plans, try: “Ask Claude to challenge this plan: what assumptions could fail, and what simpler approach would fit our constraints?”
After an on-demand review, pair review can add ongoing feedback. Pairing requires explicit opt-in; setup leaves it off.
A host is the assistant you work in; a provider is the model you consult.
| Host | Experience |
|---|---|
| Claude Code | Reviews, plan critique, comparisons; isolated reviewers and opt-in per-edit pairing |
| Codex, Cursor, Grok Build, Gemini CLI | Tools and portable workflows; pairing on demand |
| Antigravity | Tools; setup prints a manual step for workflows |
| Pi 0.83.0+ | Native tools and portable workflows; opt-in per-edit pairing |
| Claude Desktop | Tools only |
| OpenCode | Tools and portable workflows; setup verified with fixtures only |
See host compatibility for the complete matrix and manual setup limits, including existing Codex registrations.
| Provider | Access |
|---|---|
| Codex | Your authenticated Codex CLI/account |
| Claude | Your authenticated Claude Code account; consult it from a host other than Claude Code |
| Grok | Authenticated Grok Build, an exact Cursor model, or the explicit metered xAI API option |
| Antigravity | Your authenticated agy subscription; execution is off by default, and opt-in has no read-only guarantee |
| Ollama | Local models on your machine |
| Gemini | An eligible Gemini Code Assist Standard/Enterprise seat |
Cursor Agent can also consult exact models from your Cursor catalog. It is a connection route, with usage governed by your Cursor plan.
Review runs use read-only provider controls; the assistant you work in remains the editor. Antigravity refuses execution until explicitly enabled and cannot guarantee read-only access after opt-in. Review only material you are allowed to share with the selected provider.
Calls consume your existing provider plan's quota or follow that account's billing. Grok's xAI API is a separate, metered option requiring an API key; Ask LLM never enables billing or overage for you. Ollama supports local inference. Ask LLM sends no telemetry; provider and host data policies still apply.
Agreement between models is not proof of correctness. Validate findings against the code, tests, and your requirements. See data flow and costs and fallbacks.
Follow the migration guide before retiring earlier registrations.
Upgrade or remove · Troubleshooting · Documentation
Contributions: CONTRIBUTING.md. Licensed under MIT.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @ask-llm/codex-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-lykhoyda-ask-codex": {
"command": "npx",
"args": [
"-y",
"@ask-llm/codex-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@ask-llm/codex-mcpnpmio.github.Lykhoyda/ask-codex works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.