How to Have Codex Review Claude Code's Work

Have Codex review Claude Code's changes. Compare the official and Macshop plugin paths, choose one or several reviewers, and verify findings before editing.

You can ask Codex to review a change without leaving Claude Code. Two paths are OpenAI's Codex plugin and the Macshop plugin. Choose by your existing accounts and where you want the review to run, rather than assuming there is only one integration.

Choose your review path

PathWhen it fitsWhat to check
OpenAI's Codex pluginYou want the official Codex workflow inside Claude Code.Your local Codex sign-in, eligibility, and associated costs.
Macshop pluginYou want reviews in an Macshop Workspace, or several supported Agents reviewing the same change.Your Workspace, available execution options, and plan or credits.

This is a workflow comparison, not a claim that one route produces better reviews or always costs less. The steps below use Macshop; use the official repository for OpenAI's plugin instructions.

Install and connect the Macshop plugin

In Claude Code, run:

/plugin marketplace add agent-space-hq/agent-space-plugins/plugin install agent-space@agent-space

Then type /mcp, choose agent-space, and sign in to Macshop in the browser. Ask “have Codex review my changes,” or use the plugin's /agent-space:review command and specify the reviewer and scope.

Claude Code sends the requested diff and context to a Codex Agent in your Macshop Workspace. The findings return to the conversation, and the review uses your Macshop plan or credits rather than requiring a separate ChatGPT subscription for that review.

What happens when you ask

  1. Claude Code collects the change. The current plugin defaults to git diff HEAD and can include new, untracked files you want reviewed. Specify a base branch when you want the branch's changes instead.
  2. It tells you which Agents will review, that the diff goes to Macshop, and that the work uses your plan or credits.
  3. It selects the Workspace and supported execution options, then starts the review Sessions.
  4. Each reviewer receives the change and a self-contained instruction to inspect it, not to modify files.
  5. Findings return with file locations, severity, suggested fixes, and a verdict. You decide what to verify and change.

The full reviews also remain in the Workspace for its members to inspect. The documented plugin workflow is not a claim that we performed a paid review test for this article.

One reviewer or several?

For a second opinion, start with one reviewer. When several perspectives are useful, name the Agents you want to review the same change. The current plugin supports a review panel and merges findings, placing problems reported by several reviewers first.

Agreement is a signal to investigate, not proof of a bug. Different Agent harnesses do not automatically mean different underlying models; check the execution choices. More reviewers can also consume more allowance or credits.

Working with Codex and Claude Code together can separate implementation from review. It does not remove the need for your own checks. Use a review checklist for AI-generated code, inspect the reported locations, and reproduce the problem or check it with a relevant test before accepting a fix.

What is sent, and what is not

The reviewer receives the text included in the request: the diff and necessary context. It cannot browse your computer or inspect files that were not supplied. The plugin asks you to narrow a large diff rather than treating every review as a full-repository audit.

Remove secrets and unrelated private material before sending a request. Data sent for review passes through Macshop and the model provider. If a finding depends on missing context, provide the relevant material instead of assuming the reviewer has already seen it.

Review and repair are separate steps. Check the evidence and authorize changes rather than automatically accepting every suggestion.

Without the plugin

The plugin provides a workflow on top of the Macshop MCP server. You can connect the server directly and request a review in your own words:

claude mcp add --transport http agent-space https://agent.space/mcp

Other clients that support remote MCP servers with OAuth can connect too. From a supported client, you can also ask for a Claude Code review instead, using the available harness and execution choices. See the Claude Code MCP setup guide.

Start with a small review

Choose a bounded change without sensitive information. Confirm its scope, reviewer, Workspace, and funding, then check the returned findings before changing code.

A review is one part of a multi-agent coding workflow, not a substitute for tests or human approval.

Want a second opinion from Codex without leaving your Claude Code conversation? Open Macshop to prepare your Workspace and check model access and costs, then connect the Macshop plugin using the steps above. Start with one small diff and ask Codex to review it; check the returned evidence before authorizing a fix.