Codex app: precautionary-message acknowledgement appears not to persist, causing an endless confirmation loop

What version of the Codex App are you using (From “About Codex” dialog)?

26.901.6511.0, verified from the installed OpenAI.Codex Windows package on 6 September 2026. This is the currently installed package version; the About Codex display version was not separately captured.

What subscription do you have?

Not specified in this report.

What platform is your computer?

Microsoft Windows 11 Pro, version 10.0.26200, x64.

What issue are you seeing?

I am experiencing a repeated precautionary-message acknowledgement loop in the Codex desktop app on Windows, referred to as the ChatGPT/Codex app in my earlier reports.

The app displays a precautionary message requiring my acknowledgement. I acknowledge it and authorise continuation. Work resumes, but another acknowledgement is then required. Repeating the acknowledgement does not let the affected conversation progress normally.

Precautionary message appears → I acknowledge it → work resumes → another acknowledgement is required → repeat.

The bug I am reporting is the acknowledgement and continuation workflow. The acknowledgement appears not to be retained or recognised, or the same condition may be getting triggered again. These are possible explanations to investigate, not a confirmed diagnosis.

This also blocks attempts to investigate the problem using the app: the investigation itself encounters the same repeated confirmation loop. Codex has become effectively unusable for my affected workflow, and I cannot carry on with that work normally until this is resolved.

What steps can reproduce the bug?

This is the sequence I encounter in an affected conversation, rather than an independently verified minimal reproduction in a new conversation:

1. Open the affected conversation in the Codex desktop app.
2. Attempt to continue the task and receive the precautionary message.
3. Acknowledge the precaution and authorise continuation.
4. Let the task resume.
5. Receive another request to acknowledge the precaution.
6. Acknowledge again; the loop repeats instead of allowing normal progress.
7. Attempts to use the app to investigate the loop also encounter repeated acknowledgement requests.

What is the expected behavior?

Acknowledging the displayed precaution should resolve that particular pause and allow the authorised task to continue. The app should not repeatedly require acknowledgement of the same condition after I have already reviewed it and authorised continuation.

If a later pause concerns a genuinely new event, the app should make the new event and the reason for requiring another acknowledgement clear.

Additional information

• I have already reported this through /feedback and contacted OpenAI on X. The problem remains unresolved.
• Related report: https://github.com/openai/codex/issues/43041. That report concerns a precautionary pause in the VS Code extension after explicit authorisation. This report adds the repeated acknowledgement/continuation loop in the desktop app; a shared underlying cause has not been established.
• The precise warning body, selected model in the affected conversation, and existing feedback/session ID were not captured for this public report. No private conversation transcript or project diagnostics are attached.

Please explicitly track the repeated acknowledgement loop in the desktop app. Investigate whether acknowledgement is received and retained, whether continuation recognises it, and whether the same condition is being generated repeatedly after acknowledgement.

Please provide a supported recovery procedure for affected conversations and identify any fix, release, or build tracking this problem. Please also advise how to correlate this issue with my existing in-app feedback through a private support channel.

No source file, test, or entry point is named. Start by reproducing the loop in the Windows desktop app using the reported acknowledgement sequence, then trace the acknowledgement and continuation flow with appropriate diagnostics. Done means one acknowledgement permits the authorised task to continue, while genuinely new pauses clearly request separate acknowledgement.