codex - 💡(How to fix) Fix Getting "This chat was flagged for possible cybersecurity risk" on a non-cybersecurity related task. [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19601Fetched 2026-04-26 05:14:05
View on GitHub
Comments
3
Participants
3
Timeline
9
Reactions
0
Author
Timeline (top)
commented ×3labeled ×3cross-referenced ×2closed ×1

Error Message

I'm constantly getting the "This chat was flagged for possible cybersecurity risk" error that stops GPT 5.5 from working. I'm working on a decompiler for a game, it's not cybersecurity work. I tried doing KYC verification but it failed for me, and now I can't even work on this non-cybersecurity project.

RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.125.0

What subscription do you have?

Pro $100

Which model were you using?

gpt-5.5

What platform is your computer?

No response

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

No response

What issue are you seeing?

I'm constantly getting the "This chat was flagged for possible cybersecurity risk" error that stops GPT 5.5 from working. I'm working on a decompiler for a game, it's not cybersecurity work. I tried doing KYC verification but it failed for me, and now I can't even work on this non-cybersecurity project.

What steps can reproduce the bug?

Uploaded thread: 019dc69a-35b9-7593-834a-f0549d8df49d

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The "This chat was flagged for possible cybersecurity risk" error may be resolved by re-attempting KYC verification or providing additional context about the project to avoid false positives.

Guidance

  • Review the project's content and ensure it does not contain any keywords or patterns that could trigger cybersecurity risk flags.
  • Re-attempt KYC verification to provide more information about the project's purpose and intended use.
  • Consider reaching out to support to provide more context about the decompiler project and its non-cybersecurity nature.
  • Check if there are any specific guidelines or restrictions for using GPT-5.5 models for projects like decompilers.

Notes

The issue may be related to the project's content or the KYC verification process, but without more information about the project or the verification attempt, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Provide additional context about the project to avoid false positives, as the issue seems to be related to the project's content being misflagged as a cybersecurity risk.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Getting "This chat was flagged for possible cybersecurity risk" on a non-cybersecurity related task. [3 comments, 3 participants]