openai / openai/codex-plugin-cc
feat: /codex:review should not ask by default — auto-decide wait vs background
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 33.3k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
Problem
/codex:review currently calls AskUserQuestion whenever neither --wait nor --background is passed, forcing the user to pick between Wait for results and Run in background on every invocation.
This is especially painful when /codex:review is embedded in a multi-step plan: execution halts at the question prompt and the user has to come back to click through it, defeating the purpose of running the plan unattended.
Asking by default feels wrong for a command that already has all the signal it needs (git status / git diff --shortstat) to make the decision itself.
Proposal
Make auto-decide the default. Drop the AskUserQuestion step when no flag is passed, and use the existing heuristic directly:
- Tiny change (≈1-2 files, no broader directory-sized work) → run in foreground (
--wait) - Otherwise → run in background (
--background)
--wait / --background remain as explicit overrides for users who want to force a mode.
Optionally, expose a user-level default in companion config (see also #213) so power users can pin wait, background, or auto:
```json
{
"reviewExecutionMode": "auto" | "wait" | "background"
}
```
with auto being the new default.
Why this is safe
- The heuristic already exists in
commands/review.md— the change is just "apply it automatically instead of asking." - Background mode is non-destructive: results are retrievable via
/codex:status. - Users who preferred the prompt can set
reviewExecutionMode: "wait"or always pass--wait.
Impact
- Plans containing
/codex:reviewrun end-to-end without human intervention. - One less interactive step for the common case.
- No loss of control — flags still work.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with commands/review.md, where the existing git status/diff heuristic and AskUserQuestion flow are described. Trace the no-flag path first, then verify that explicit --wait and --background overrides remain unchanged; done means a review invocation selects foreground or background automatically without prompting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100