After Codex finishes work, you review its changes, leave inline comments, and send feedback for another pass. This review-feedback-fix loop repeats until you are satisfied.

​
1. Open the changes panel

There are three ways to open the changes panel:
  • Click the Toggle Changes Panel button in the navbar
  • Click the changes icon in the app bar
  • Open the command bar from its icon in the navbar or with Cmd/Ctrl + K, then search for “Show Changes Panel”
The changes panel shows the diff viewer in the centre and the file tree on the right.

​
2. Navigate the file tree

The file tree shows all files that were added, modified, or deleted. Click any file to load its diff in the viewer. Use the search box at the top to filter files by name. The toggle button in the search bar lets you expand or collapse all folders at once.
Start with the files you care most about — the main feature file or the entry point — rather than reviewing alphabetically. This gives you context for the rest of the changes.

​
3. Read diffs

The diff viewer uses colour coding to show what changed: green for additions, red for deletions, and grey for unchanged context lines. You can switch between two view modes: You can also switch views from the command bar (Cmd/Ctrl + K → “Switch to Side-by-Side View”).

​
4. Add inline comments

To leave feedback on a specific line, hover over it in the diff and click the comment icon that appears. Write your comment and submit it. Good comments are specific and actionable. Here are some examples:
Comments are not sent individually. They are collected and submitted together when you send a message in the chat.

​
5. Send feedback to Codex

After adding your comments, send them to Codex. You can include an optional message for extra context, or just send the comments on their own. A badge shows how many review comments will be included. Codex sees all inline comments as context and works through them.

​
Troubleshooting

  • Codex may not have made any changes yet. Check the workspace status.
  • If all changes were committed and pushed, the panel resets. Check the Git section for the most recent commit.
Comments are consumed when you send a message. They become part of the chat history. Add new comments for the next review round.
Be more specific. Instead of “this is wrong”, explain what is wrong and suggest a fix. Reference exact line numbers or variable names so Codex knows exactly where to look.

​
Next steps

Issue Management

Create and organise issues on the kanban board

Browser Testing

Preview your app in the built-in browser

Changes Panel

Full reference for diff viewer and comment features

Git Operations

Create pull requests, rebase, merge, and manage branches