Codex App does not indicate whether Trusted Access is missing or insufficient after verification

[jason5545]

Codex App version:
26.623.141536 (4753)

Subscription:
ChatGPT Pro 5x

Platform:
Darwin 25.5.0 arm64 arm

What issue are you seeing?
Trusted Access verification appears to be completed successfully on the web, but the Codex App still shows a warning/block for the same type of task.

The web verification page shows that my identity has been verified and that Trusted Access is enabled. After that, I fully signed out of Codex, signed back in, quit the Codex App completely, and reopened it. The same type of Codex warning/block still appears.

The main issue is that Codex does not make it clear which state applies:

• Trusted Access is not detected / not active for the current Codex session
• Trusted Access is active, but this specific request still requires additional access, further review, or a higher trust level

Those are very different cases. From the user side, the web account state appears enabled, but Codex does not expose whether the current app session has actually picked up the entitlement.

Please treat this as a product/session-state and error-message clarity bug report, not an account support request. I have already contacted OpenAI Support separately.

I saw that there are other safety-check / Trusted Access reports in the issue tracker. This report is specifically about the missing distinction between "Trusted Access is not active for this Codex session" and "Trusted Access is active but insufficient for this request."

What steps can reproduce the bug?

1. Complete Trusted Access verification through the web flow.
2. Confirm that the web verification page shows Trusted Access as enabled.
3. Fully sign out of the Codex App.
4. Sign back in.
5. Quit the Codex App completely and reopen it.
6. Start a Codex task that previously triggered the Trusted Access warning/block.
7. Observe that Codex still shows a warning/block, without clarifying whether Trusted Access is missing from the session or active but insufficient for the request.

Expected behavior:
After Trusted Access verification is complete and the user signs out/in, Codex should either:

• pick up the updated Trusted Access entitlement, or
• clearly say that Trusted Access is not active / not detected for the current Codex session, or
• clearly say that Trusted Access is active but the request still requires additional access, further review, or a higher trust level.

Ideally, Codex should expose a visible account/access status somewhere in the app or CLI so users can verify whether Trusted Access is active for the current session.

Additional information:

• OpenAI Support case: 11016613.
• Screenshots showing the enabled web verification page and the Codex warning/block have already been attached to that support case.
• Verification page was viewed in Helium.
• Codex CLI installed locally: codex-cli 0.142.3.

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• False "Cyber Abuse" Policy Flag for Legitimate Reverse Engineering Work #30271

Powered by Codex Action

[jason5545]

I reviewed #30271. It is related, but I do not think this issue is an exact duplicate.

#30271 is mainly about a legitimate reverse-engineering workflow being flagged as Cyber Abuse after cyber verification.

This issue is narrower: Codex does not distinguish between two different states after Trusted Access verification:

1. Trusted Access is not active / not detected for the current Codex session
2. Trusted Access is active, but the specific request still requires additional access, further review, or a higher trust level

That distinction matters because the user action and expected product behavior are different in each case.