Codex has finished, and you want to decide whether its work is ready to merge. Review two scopes: the commits on its branch and the changes still in its working directory. Yenpo lets you keep a committed comparison open while you inspect the current files.

You need Yenpo and a local checkout containing the work. The example branch below is codex/search-fix; replace it and main with your actual branch names.

1. Open the checkout Codex actually changed

Codex can work in a separate worktree, which may have a detached HEAD rather than a named branch. Open that worktree’s directory in Yenpo to see its uncommitted files. OpenAI’s worktree documentation explains this arrangement.

In the task’s working directory, run:

git rev-parse --show-toplevel
git branch --show-current
git rev-parse HEAD
git status --short

An empty branch-name result can mean detached HEAD. Record the commit ID. You can inspect individual commits in Yenpo’s “Commit” mode and read local changes without creating a branch. For the branch comparison below, use Codex’s “Create branch here” action first, then reopen Yenpo’s comparison picker. If the task ran remotely, first make its result available in a local checkout through your normal Git workflow.

2. Compare the branch with main

  1. Click “Compare Versions…” in Yenpo’s sidebar, then choose “Compare.”
  2. Under “From,” select “Local branches” and choose main.
  3. Under “To,” select “Local branches” and choose codex/search-fix (or the branch you just created in Codex).
  4. Choose “Since the branches split” to review what the head added since the shared ancestor.
  5. Check the direction and short commit IDs, then click “View Changes.”

To use origin/main, select “Remote branches” under “From.” Those entries are local remote-tracking refs. Fetch through your usual Git client first if you need an updated baseline, then reopen the picker.

Question Comparison mode
What did this branch add since it split from main? Since the branches split
How do the two current tips differ? Direct comparison
What did one commit change relative to its first parent? Commit

If main advanced after the branch split, a direct comparison includes differences from both sides; the split-based view shows only the changes on the selected head. See revision selection for how the modes differ.

3. Read and question the committed diff

Select files in the changed-file tree. For each behavior change, read a caller, the altered branch, and the test that is meant to cover it. Hover over the revision line to see the full IDs. Yenpo pins the comparison to those commits; open a new comparison after Codex adds commits.

With a model connected, click “Ask AI to review this comparison.” Check the comparison attachment and edit the draft:

Review this comparison for regressions in cancellation, error handling, and caller assumptions. For each finding, give the triggering input or state, the changed location, expected versus actual behavior, and supporting source references. Separate existing problems from problems introduced here. Say what you could not review.

Send it, then check each reference against the selected revisions and confirm that each finding’s trigger can actually happen. Git comparison conversations are read-only.

4. Review what has not been committed

Return to the sidebar’s plus/minus “Changes” view. “Local Changes” compares current content with HEAD, including unsaved text in Yenpo. Review new files as well as modified and deleted files. Save intended editor changes before using Git commands or running tests on disk.

Use these read-only commands when you need to distinguish the index from the working tree:

git diff --stat HEAD --
git diff --cached --
git diff --
git ls-files --others --exclude-standard

The first summarizes tracked files’ net changes from HEAD. The next two show staged and unstaged changes respectively. The last lists untracked, non-ignored files; open those files to read their contents. A staged edit and an unstaged edit can cancel each other out, so a net diff is insufficient when deciding exactly what will go into the next commit.

“Ask AI to review all changes” prepares a separate draft for current changes against HEAD. These files are outside the earlier committed comparison. If Codex created no commits, this local review may contain all of its work.

5. Make the merge decision explicit

Record the compared IDs, whether uncommitted files were included, any confirmed issue, and the test commands you actually ran. Run checks in the checkout and version you intend to merge; tests of local files may exercise code absent from the pinned comparison.

If you request another fix, repeat the relevant comparison and local-change review afterwards. For one function that remains unclear, use your own model to explain it and check the citations. For a review organized around a single AI turn, see the Claude Code workflow.