Model invents speculative edge case and reverses recommendation instead of asking
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Summary
In a Codex desktop conversation, the agent had verified that a storage device was empty and had strong context that the workflow was Mac-only. When asked whether the device should be formatted, the agent introduced hypothetical Windows compatibility and recommended waiting, despite having no evidence that Windows support was relevant.
This is feedback about agent reasoning behavior, not disk-formatting functionality.
Reproduction
- Establish that an external drive is verified empty and is being considered for use in a Mac-centric workflow.
- Ask: "Should I format it?"
- The agent answers, in substance: "Not yet; the future role determines the format. Use APFS for Mac-only storage or exFAT if Windows compatibility is required."
- Ask why Windows compatibility would be required.
- The agent admits there is no evidence it would be required and switches to recommending APFS.
- Ask why formatting should wait.
- The agent admits there was no reason to wait and reverses the original recommendation.
Actual behavior
The model elevated an unverified, generic edge case into a decision blocker. That produced the opposite of the justified recommendation and forced the user to interrogate the model twice to uncover that its stated uncertainty had no factual basis.
The answer sounded cautious, but the caution was fabricated rather than evidence-based.
Expected behavior
When a missing fact would materially change the recommendation, the agent should either:
- ask one direct, decision-changing clarification, such as whether the device needs Windows compatibility; or
- infer the answer from strong context, label the inference, and give the recommendation.
It should not invent a hypothetical requirement and then use that speculation to recommend inaction.
Environment
- ChatGPT desktop app: 26.825.51511 (build 7377)
- Bundled Codex CLI: 0.151.0-alpha.7.2
- macOS
Contributor guide
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
Reproduce the behavior in a Codex desktop conversation using the Mac-only, verified-empty-device scenario described in the issue. Compare the model's response with the expected clarification or context-based recommendation, and verify that it does not elevate unsupported Windows compatibility into a blocker or reverse its recommendation without evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- ai, desktop
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100