codex - 💡(How to fix) Fix Plan Mode rejection should support inline feedback before revising the plan [1 participants]

Summary

Plan Mode should support a first-class "reject with feedback" path when the user declines a proposed plan.

Right now, rejecting or declining a plan is too coarse for a common real workflow: the user does not want to abandon the plan, they want to explain what is wrong with it so Codex can revise it. The missing piece is an inline feedback input immediately after rejection.

Current behavior

When Codex proposes a plan, the approval UI generally treats rejection as a decision separate from the user's actual critique. The user then has to manually type a follow-up in the normal composer, and the model may or may not interpret it as structured plan revision feedback.

In practice, users reject plans because of specific defects:

• scope is too broad or too narrow
• implementation order is wrong
• tests or validation are too weak
• a risky migration is missing
• UI/UX details are underspecified
• assumptions are wrong

The UI does not make that critique path explicit.

Expected behavior

After the user chooses Reject / Revise / Do not implement, the TUI should move focus into an inline feedback composer tied to that plan decision.

A minimal version would be enough:

1. User receives a proposed plan.
2. User selects Reject / Revise.
3. TUI opens a focused feedback input.
4. User types a short reason such as testing is too weak; include device validation.
5. Codex receives this as plan-revision feedback and produces a revised plan, instead of treating the turn as an unrelated chat message.

A keyboard path such as Tab from the rejection choice into the feedback input would make this especially smooth.

Why this matters

Plan Mode is most useful when the user can steer the plan before implementation. A binary accept/reject interaction is too low-bandwidth for large engineering work.

For serious refactors, rejecting a plan almost always means "revise this with these constraints," not "discard this topic." Making that explicit would reduce repeated plan loops and make the approval step much more useful.

Related issues

Related but not the same:

• #23341: implementation approval can remain stuck in Plan Mode
• #19921: expose plan-mode prompts through hooks
• #19328: expose TUI question prompts to hooks
• #18611: improve Plan Mode decision prompts
• #19964: unable to add information in Plan Mode

This issue is specifically about the human UI path for giving structured feedback when rejecting a proposed plan.