codex review should provide a way to add prompt to the review tasks
Resolved 💬 5 comments Opened Dec 10, 2025 by doggy8088 Closed Mar 29, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What feature would you like to see?
Currently, when I use the --base or --commit flag, I can't utilize the PROMPT. However, there are times when we need to provide additional instructions to the codex review.
<img width="1008" height="186" alt="Image" src="https://github.com/user-attachments/assets/32c5b547-6df9-4bd9-8e74-ea919d0bf28a" />
Additional information
Run a code review non-interactively
Usage: codex review [OPTIONS] [PROMPT]
Arguments:
[PROMPT] Custom review instructions. If `-` is used, read from stdin
Options:
-c, --config <key=value> Override a configuration value that would otherwise be loaded from `~/.codex/config.toml`. Use a dotted path
(`foo.bar.baz`) to override nested values. The `value` portion is parsed as TOML. If it fails to parse as TOML, the raw
string is used as a literal
--uncommitted Review staged, unstaged, and untracked changes
--base <BRANCH> Review changes against the given base branch
--enable <FEATURE> Enable a feature (repeatable). Equivalent to `-c features.<name>=true`
--commit <SHA> Review the changes introduced by a commit
--disable <FEATURE> Disable a feature (repeatable). Equivalent to `-c features.<name>=false`
--title <TITLE> Optional commit title to display in the review summary
-h, --help Print help (see more with '--help')
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
This is actually important, yes.
@etraut-openai Opened a PR for this: Can be found here :) When you have a moment please let me know what you think! https://github.com/openai/codex/pull/11903
@etraut-openai
Thanks for keeping this issue open. I understand the new contribution policy (invitation-only), so I’m sharing
implementation analysis rather than requesting PR review.
I built a working prototype in my fork that adds optional extra instructions at the end of the
/reviewpreset flow:Implementation notes:
additional_instructions: Option<String>onReviewRequestPrototype branch/commits (for reference only):
Question for maintainers: does this direction align with intended
/reviewUX, and should this be pursued as:1) TUI/App first, then CLI parity, or
2) a cross-surface design in one invited effort?
This feature request hasn't received enough upvotes, so I'm closing it.