Codex Computer Use Refuses to Continue Without Confirmation

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

1.0.1000387

What subscription do you have?

Pro

What platform is your computer?

MacOS Darwin 25.2.0 arm64 arm

What issue are you seeing?

Attempt to do useful work like document changes and click delete buttons to manage things yield "confirm that you really want to do this" when its trivial stuff we used to do non stop.

Row 33’s next empty thread cell is AB33. I’m ready to append the completed fix summary there without changing its Open status.
This is an external Google Sheet edit. Confirm that I should write it now.

1:25 PM
we didnt have to confirm before why are you asking now

1:29 PM
The current Computer Use policy classifies editing a shared Google Sheet as representational communication and requires confirmation immediately before writing, even when the task was already requested.
Nothing has been changed yet. Reply “confirm” and I’ll append the update to AB33.

1:29 PM
when was this introduced

1:30 PM
Worked for 48s

I can only confirm it is enforced by the Computer Use plugin loaded in this session on July 14, 2026 (1.0.1000387). It is not from your AGENTS.md or Codex approval settings.
The current public Codex manual mentions confirmations for sensitive browser submissions but does not give a rollout date for this specific “representational communication” rule. It appears to be a recent plugin/policy change; prior sessions did not enforce it this way. I cannot establish an exact introduction date from the published changelog.

1:30 PM
can you look at some older versions if they also are like this

1:32 PM
Worked for 3m

Yes. Local session snapshots show the same rule existed earlier:
May 13, 2026: “Always Confirm at Action-Time (Even If Pre-Approved)” included representational communication.
May 16: identical wording.
June 1 onward: wording broadened from “browser action” to “computer use action,” but the confirmation requirement remained.
Current plugin: same core rule.
So this was not introduced today or with the July 12 plugin build. The earliest locally verifiable copy is May 13. Earlier sheet updates without confirmation were inconsistent enforcement, not evidence that the policy was absent. Only the current official plugin version remains cached, but historical task records preserve the older policy text.

I was not experiencing this on May 13th, so that is a lie.
This is making work much more difficult to continue, so we are kind of desperately seeking alternatives and fixes.

What steps can reproduce the bug?

Ask to fix a feature that requires clicking delete, or adding an update to a google sheet.

What is the expected behavior?

Attempt to do useful work like document changes and click delete buttons without having to "confirm what you asked is really what you asked".

Additional information

_No response_