### Steps to reproduce 1. In the Codex app, work on a normal app project (no cyber content). 2. The system flagged the conversation for "cyber" and blocked coding progress. 3. After submitting feedback in the Codex app, the app keeps routing me to GPT-5.2 Codex instead of the normal experience. ### Expected behavior No false "cyber" flag for normal app development, and no forced routing to GPT-5.2 Codex for a paying customer. ### Actual behavior Normal coding was flagged as "cyber" and I was r

Potential duplicates detected. Please review them and close your issue if it is a duplicate. - #12172 - #12171 - #12168 - #12165 - #12160 *Powered by [Codex Action](https://github.com/openai/codex-action)*

Bug: incorrectly flagged for cyber while building app; routed to GPT-5.2 Codex

Resolved 💬 4 comments Opened Feb 18, 2026 by integrate-your-mind Closed Feb 20, 2026

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Steps to reproduce

In the Codex app, work on a normal app project (no cyber content).
The system flagged the conversation for "cyber" and blocked coding progress.
After submitting feedback in the Codex app, the app keeps routing me to GPT-5.2 Codex instead of the normal experience.

Expected behavior

No false "cyber" flag for normal app development, and no forced routing to GPT-5.2 Codex for a paying customer.

Actual behavior

Normal coding was flagged as "cyber" and I was routed to GPT-5.2 Codex afterwards.

Additional context

Thread included in the template/URL: 019c7212-9a63-7001-9148-09da01b44d7f.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 6 months ago

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

#12172
#12171
#12168
#12165
#12160

Powered by Codex Action

integrate-your-mind · 6 months ago

Same issue here.

Case number (email support): 05871927
Org ID: org-L7aA0Kvm5HadDY6ICWq10n5l
User/email: elon@goodboylabs.com
Model: gpt-5.3-codex (now routed to gpt-5.2 with a “verify identity” hover)
Identity verification completed but access still restricted
Time range (EST): Tue Feb 17 ~11 PM to Wed Feb 18 ~10 AM
request_ids: none
Compromise: none suspected; OAuth login only; no API key exposure. Likely caused by an accidental cron job that repeatedly spawned the Codex agent while I was asleep. Job is disabled; adding guardrails/monitoring and rate limiting to prevent recurrence.

Requesting review and restore of GPT-5.3-codex access for my account/org.

ppoage · 6 months ago

Can you all please automate the rejection and deletion of all, what is now like 50, of these tickets?

etraut-openai contributor · 6 months ago

Thanks for the bug report. We're continuing to tune our cyber safety classifiers to make them more accurate. You can read more about this here. If you see this again in the future and believe it's a false positive (i.e. you aren't doing anything related to cybersecurity), please use the /feedback slash command and choose "Safety Check" to report it. That will help us further tune our checks.