Temporary cybersecurity restriction – review request (Thread ID: 019cb08e-466a-73c2-8b98-d64723a6602a)

Resolved 💬 1 comment Opened Mar 3, 2026 by SaideIsmael Closed Mar 3, 2026

Hello,

I am encountering the following restriction message when using the Codex CLI with GPT-5.3-Codex:

"stream disconnected before completion: This user's access to gpt-5.3-codex-1p-codexswic-ev3 has been temporarily limited for potentially suspicious activity related to cybersecurity."

Thread ID: 019cb08e-466a-73c2-8b98-d64723a6602a

Authentication method: ChatGPT login (no API key).

Usage context:
I am developing multiple personal productivity applications (AI browser, file management tools, file anonymizer, etc.). As part of defensive code quality, I have also implemented a “security-audit” skill that generates only security recommendations and asks Codex to suggest corrections. The output does not include exploit code or proof-of-concept attack patterns.

The frequency of calls and the security-focused prompts may have tripped automated safeguards designed for high-cybersecurity-risk contexts.

I kindly request:

  1. A review of this restriction and its removal if it is a false positive,
  2. Technical clarification on the specific request patterns that triggered the safeguard,
  3. Guidance on how to phrase and manage queries to prevent similar disruptions in the future.

Thank you for your assistance.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗