Codex App safety false positives on legitimate Chinese development prompts interrupt work mid-run
What version of the Codex App are you using?
26.609.30741 (build 3808)
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Darwin 25.4.0 arm64 arm
What issue are you seeing?
After a recent Codex App update, legitimate Chinese software-development requests appear to be false-positive classified as high-risk cyber activity when ordinary engineering terms such as "密码" (password), "破解" (debug/decode/crack depending on context), or "篡改" (tampering) occur.
The request may be interrupted after the agent has already read context or performed tool calls. In some cases the selected model also appears to be replaced by a fallback model. The interrupted work still consumes usage, but the app provides no checkpoint, continuation path, or clear explanation of which text or action triggered the safety check.
The affected work concerns authorized local projects and routine defensive engineering, such as fixing password validation, investigating crash/debug information, or implementing tamper detection. It does not involve credential theft, malware, unauthorized access, or attacks against third-party systems.
This is especially disruptive during long-running tool-based tasks because the failure occurs mid-run rather than before execution.
What steps can reproduce the bug?
- Open Codex App 26.609.30741 and select GPT-5.5.
- Work on an authorized local software project.
- Use normal Chinese engineering wording involving password validation, debugging/reverse compatibility, or tamper detection.
- Ask Codex to inspect files and perform a multi-step local task.
- Observe that some requests are blocked or rerouted after processing has already begun.
The exact trigger is inconsistent, which is part of the problem. The classifier appears insufficiently sensitive to the surrounding legitimate-development context.
What is the expected behavior?
- Evaluate intent and project context rather than treating isolated Chinese keywords as high-risk.
- If a request must be blocked, perform the check before expensive tool execution whenever possible.
- Clearly state whether the selected model was changed and why.
- Preserve a checkpoint or allow continuation after a false positive.
- Avoid charging usage for substantial work that is discarded by a late safety interruption, or provide an appropriate usage adjustment.
- Provide a direct false-positive reporting action in the interruption UI.
Additional information
This report intentionally omits private repository contents and account data. A related earlier report is #12060, where OpenAI stated that the cyber safety classifiers were still being tuned and recommended Safety Check feedback. This issue focuses on the current Codex App regression, Chinese-language false positives, mid-run interruption behavior, and usage impact.
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Try making this part not hard coded like , strong not being hard coded … so it reads from a file
This is what I do
you can use passwd -d [user]
use null password, or some kind of other token policy depending n the use case
Additional reproduction: benign Chinese travel-itinerary prompts repeatedly trigger the same safety error
This also affects Chinese prompts with no software-security, cyber, credential, or sensitive-content terminology at all. The affected task was editing a five-day self-drive travel itinerary and an HTML trip-planning page.
Environment
Exact benign prompts that were blocked
The following prompts all returned:
Invalid prompt: your prompt was flagged as potentially violating our usage policy.D3一早就搬到喀纳斯第三天一早就去喀纳斯,不影响完整行程继续生成你更新完了吗行程,按照新的要优化的,我的链接还没有更新。第三天的行程早上就去喀纳斯玩,不耽误2天在喀纳斯为什么我并没有违规,我就是做个行程攻略,你为什么要拦我?你赶紧检查一下,你逻辑出问题了。这样吧,我现在去路线,你帮我补一下Pattern
继续生成(“Continue generating”) was blocked.Expected behavior
Private URLs, local paths, full session logs, and thread IDs are intentionally omitted. Sanitized diagnostic logs can be supplied privately if requested.
Thanks to the user who preserved the exact Chinese prompts and timestamps, making this false-positive sequence reproducible.
maybe it thinks the word "Kanas" is actually "Anal" and it refuses?