The changes panel lets you review modifications in the selected host-side workspace folder and provide feedback to Codex before you push or create a pull request.

​
Why Review Changes?

Before committing or creating a PR, you should always review what Codex changed:
  • Verify correctness - Does the code do what you asked?
  • Check for issues - Are there bugs, security problems, or style violations?
  • Understand the approach - Learn what Codex did so you can explain it to reviewers
  • Provide feedback - Ask Codex to fix problems before committing
Always review changes before merging. Codex can make mistakes, introduce bugs, or misunderstand requirements.

​
Opening Changes

  • Click the Changes toggle () in the navbar
  • Click the changes icon in the context bar
  • Use the command bar: Cmd/Ctrl + K → “Toggle Changes Panel”

​
File Tree

The changes panel displays a hierarchical file tree:
  • Folders: Expand/collapse to navigate
  • Files: Click to view the diff
  • Search: Filter files by name
  • Expand/Collapse All: Quick navigation buttons

​
Diff Viewer

View code changes with syntax highlighting:

​
Diff View Modes

Toggle between two display modes: Switch modes using the diff view toggle in the navbar (when Changes panel is open) or via command bar: Cmd/Ctrl + K → “Toggle Diff View Mode”.

​
Diff Options

Customise the diff display: Access these via the command bar’s Diff Options page.

​
Giving Feedback with Comments

Add comments directly on code changes to provide feedback to Codex.

​
Adding Comments

  1. Hover over a line in the diff
  2. Click the comment icon that appears
  3. Write your feedback
  4. Submit the comment

​
Comment Uses

  • Request changes: Ask Codex to modify specific code
  • Ask questions: Get explanations about implementation choices
  • Provide context: Share additional requirements or constraints
  • Approve sections: Indicate code that looks good

​
Codex Response to Comments

When you send a message with review comments, Codex sees your feedback and acts on it. In this example, Codex restores a file after the user requested the change be reverted.
Comments are visible to Codex in subsequent messages, helping guide further development.

​
GitHub Integration

When your workspace is linked to a pull request:

​
Viewing GitHub Comments

  • Click the GitHub icon in the changes panel toolbar to toggle GitHub comments
  • Comments from the PR appear inline with the diff
  • Badge shows comment count per file
Only submitted review comments are shown. Pending reviews (not yet submitted on GitHub) won’t appear until you submit the review.

​
Linking to a PR

Workspaces automatically link when:
  • You create a PR from the workspace
  • The workspace branch matches an existing PR
Review GitHub comments alongside your changes to address PR feedback efficiently.

​
Review Workflow

Follow this workflow to effectively review and refine Codex changes:
1

Wait for Codex to finish

Let Codex complete its work. The status in the sidebar will change from “Running” to “Idle”.
2

Open the Changes panel

Click the Changes icon in the navbar or use Cmd/Ctrl + K → “Toggle Changes Panel”.
3

Review each file

Click through each modified file in the file tree. Look for:
  • Logic errors - Does the code do what you intended?
  • Missing pieces - Are there unhandled edge cases?
  • Code quality - Is the code readable and maintainable?
  • Security issues - Any obvious vulnerabilities?
4

Add comments on issues

For any problems you find, hover over the line and click the comment icon. Write specific feedback:Good comment: “This API endpoint should validate the user ID before querying the database to prevent unauthorized access.”Bad comment: “This is wrong, fix it.”
5

Send feedback to Codex

Type a message in the chat (e.g., “Please address the review comments”) and send it. Codex will see your inline comments and make corrections.
6

Re-review and repeat

After Codex addresses feedback, review the new changes. Repeat until you’re satisfied.
7

Create PR when ready

Once changes look good, create a pull request using the Git panel or command bar.
Be specific in comments. Instead of “this is wrong”, explain what’s wrong and ideally suggest a fix. The more context you give, the better Codex can correct the issue.