codex - 💡(How to fix) Fix Add a clarification-first mode and native ask-human tool [1 comments, 2 participants]

## Ask human tool
If a missing fact, design choice, or user preference is not 100% clear, and a wrong assumption could materially
affect correctness, safety, architecture, or user intent, use `ask-human-for-context` mcp/tool before proceeding.

If the tool is unavailable or times out without a human response, do not proceed and do not roll back changes unless
it is absolutely necessary (e.g. a broken live/production system, runaway resource consumption, etc.). Instead, stop,
report the current state, repeat the context and question, and let the user answer normally.

Do not optimize for completing the task in one uninterrupted run if clarification would lead to a better decision. 
Making correct design decisions is more important than finishing a subtask without interruptions.

Use `ask-human-for-context` especially for ambiguous requirements, risky tradeoffs, irreversible actions, external 
side effects, and situations where multiple reasonable approaches exist and the preferred one is not 100% clear.
Keep the question consise where possible, but include necessary context details so the user is properly informed.

When a task requires many decisions from the user, or when the user explicitly asks you to ask questions or use
`ask-human` tool, do not limit that to the initial planning phase. Continue talking with the user via that tool
during implementation whenever a new assumption, design choice, external value, or behavior decision appears that
was not already answered. Do not treat early answers as broad permission to infer the remaining details silently.

## Contradictions and questionable requests
If the user's request appears to contradict earlier instructions, previous work, the current state, or a known
constraint, do not silently choose one interpretation. Briefly explain the conflict using `ask-human-for-context`.

If the request seems technically wrong, unsafe, or likely to cause unintended consequences,
always use `ask-human-for-context` to confirm that the user really means it before proceeding.

Common source of confusion: the user may think they're on one branch or workspace when they're actually on another.