GuidesAgents side by side

Have Codex review Claude Code’s pull requests

A different agent than the author reads each PR, the tests run again on its head, and Merge says what it found.

wisp guidesUpdated Nov 11, 2026 · 2 min read

A wisp report for a finished task: headline, numbers, the diff and the test run

Claude Code’s /review is Claude reading Claude’s work, and Codex’s /review is Codex reading Codex’s. In wisp, turn on Review by another harness and each open PR is reviewed by a different agent than the one that wrote it. The project’s tests run again on the PR’s head, and Merge tells you what was found.

macOS · Linux and Windows in beta · Node 20+ · MIT

What the CLIs do on their own

Each vendor ships a reviewer for its own agent. Claude Code has /review and /security-review, and a GitHub Action that comments on PRs. Codex has /review against a base branch or a commit, and @codex review on GitHub. Cursor has Bugbot, billed per review. In each case the model that reviews the code comes from the same company as the one that wrote it, so the two tend to miss the same things.

Turn it on

Start wisp with at least two harnesses signed in, for example Claude Code and Codex.

macOS · Linux and Windows in beta · Node 20+ · MIT
Settings → General → Review by another harness. Pick Another harness than the author, or one harness by name (pick it by name to be sure the reviewer runs another company’s model).
Ship a task. Once its PR is open, the reviewer gets the branch at the PR’s head, reads the diff against the base and the code around it, and lists what it would fix by severity. At the same time, the project’s tests run again on that head.

Read it where you merge

The PR row shows Not reviewed, Reviewing, N issues, Tests fail or Reviewed. The PR panel lists each finding with its file and line, Send to agent to hand it back to the task, and Review again. Merge’s confirmation says when the PR isn’t reviewed or what the review found. Merge stays possible: the review informs you, it doesn’t block.

Questions

Does the review post comments on GitHub?

No. Findings show in wisp: on the PR row, in the PR panel and in Merge’s confirmation. Send to agent hands one back to the task to fix.

Which harness reviews?

With Another harness than the author, the first one installed that didn’t write the task: Claude Code, then Codex, then the rest. Or pick one by name.

Does it block Merge?

No. Merge’s confirmation tells you what the review found, or that it hasn’t run, and you decide.

Can a spell change it?

Yes. The review setting can be set by a spell, and the PR chip and panel section can be restyled (split.pr.review, panel.pr.review).

Try it on your own repo

One command starts wisp in this folder. It runs the agent CLIs you already have, signed in as you.