We use custom skills to run staged workflows in Codex, for example:
intent.md → spec.md → review/approve ->plan.md → build → review
At each stage, the skill needs to ask a small structured question or present an approval gate. Currently, request_user_input is available only in Plan mode. This creates a conflict between two separate workflows:
- I enter Plan mode only to access the structured question UI.
- The skill drafts
intent.mdand asks me to approve it. - After approval, Codex’s built-in Plan mode starts producing an implementation plan.
- The skill’s workflow actually requires
spec.mdnext, with its ownplan.mdstage later.
The result is two competing planning lifecycles. It feels like taking two steps forward and one step back, and Codex can lose track of which artifact should come next.
Claude can display equivalent structured questions during normal execution, without entering a separate planning mode. That makes iterative, gated workflows much smoother.
Requested change
- Make
request_user_inputavailable in Default mode. - Treat structured questions as a mode-independent UI capability.
- Calling it should pause for the user’s response without starting or approving Codex’s built-in Plan-mode lifecycle.
- Keep existing Plan-mode behavior for users who explicitly want Codex to produce an implementation plan.
Why this matters
Structured choices are useful beyond upfront planning. Skills need them for:
- requirements interviews;
- artifact approval gates;
- design tradeoffs;
- migration decisions;
- review findings;
- other multi-stage workflows.
Ideally, the active collaboration mode should control Codex’s overall behavior, while request_user_input only controls how a question is presented.