Trusted Access account still receives cyber safety block and model rerouting

Open 💬 2 comments Opened Aug 9, 2026 by thanhdat317
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.147.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.5 codex

What platform is your computer?

_No response_

What terminal emulator and version are you using (if applicable)?

_No response_

Codex doctor report

What issue are you seeing?

My account has been approved and identity-verified for Trusted Access for Cyber. The verification page states: “You’re verified” and confirms that Trusted Access is currently activated.

During legitimate analysis of an authorized, temporary, and isolated CTF challenge, Codex replaced its response with:

This content can't be shown We take extra caution with cybersecurity requests. If you’re a security professional, you may be able to apply for Trusted Access.

The message links to the Enterprise Trusted Access application even though individual Trusted Access is already active on my account. Before the response was blocked, the interface also reported that the model had changed to gpt-5.5 high and then gpt-5.5 xhigh.

I understand that Trusted Access does not remove all safety controls. The problem is that the error incorrectly instructs an already verified user to apply again, making it unclear whether Trusted Access is not being recognized or whether this is a request-level safety decision.

What steps can reproduce the bug?

Uploaded thread: 019fe58c-ce8c-72e1-89ee-7a19995f28a5

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 19 days ago

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

  • #36785
  • #36671

Powered by Codex Action

JimmyJones97 · 13 days ago

Seeing the same issue constantly, even when working on local machine with no network connection.

01a000f0-dfea-7470-8a6b-e347915ba7f

Trusted Access already approved, using gpt-daybreak-blue-latest, even basic reverse engineering is blocked.