Add step-level “Copy git apply” / “Copy patch” to Codex desktop app

Open 💬 1 comment Opened Jun 6, 2026 by IarBest

What variant of Codex are you using?

Codex app

What feature would you like to see?

Hi!

I would like to request the same kind of patch-copying workflow in the Codex desktop app that exists in Codex Web.

In Codex Web, the “Copy git apply” action is especially useful because it copies the patch for the specific Codex step / latest response, not necessarily the entire accumulated diff from the base branch.

This matters a lot for iterative AI-assisted review workflows:

  1. Codex makes an initial change.
  2. I copy that step’s patch and send it to another assistant/person for review.
  3. The reviewer finds issues.
  4. I send follow-up instructions to Codex.
  5. Codex makes additional fixes.
  6. I copy the patch again.

At step 6, I do not want the whole accumulated diff from main/base. I want only the changes introduced by the latest Codex step, so the reviewer can inspect exactly what changed in response to the last instruction.

Suggested actions in the Codex desktop app diff/review UI:

  • Copy patch for this step
  • Copy git apply patch for this step
  • Save patch for this step as .patch
  • Copy full accumulated diff from base
  • Save full accumulated diff from base as .patch

It would be helpful if the UI made the distinction clear:

  • “This step only”
  • “All changes from base”
  • “Current local worktree”

This is especially important for users who are not deeply comfortable with Git yet. The command-line workaround for full diffs is manageable:

git diff HEAD > changes.patch

But reproducing a clean step-level patch locally requires manually capturing the state before and after each Codex action, which is much less discoverable and more error-prone.

Please consider adding consistent step-level patch export to the desktop app, matching the very useful Codex Web workflow.

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗