To those wondering about their rationale for this.
It would be great if the HN title could be changed to something more like, 'OpenAI requiring ID verification for access to 5.3-codex'?
> Thank you all for reporting this issue. Here's what's going on.
> This rerouting is related to our efforts to protect against cyber abuse. The gpt-5.3-codex model is our most cyber-capable reasoning model to date. It can be used as an effective tool for cyber defense applications, but it can also be exploited for malicious purposes, and we take safety seriously. When our systems detect potential cyber activity, they reroute to a different, less-capable reasoning model. We're continuing to tune these detection mechanisms. It is important for us to get this right, especially as we prepare to make gpt-5.3-codex available to API users.
> Refer to this article for additional information. You can go to chatgpt.com/cyber to verify and regain gpt-5.3-codex access. We plan to add notifications in all of our Codex surfaces (TUI, extension, app, etc.) to make users aware that they are being rerouted due to these checks and provide a link to our “Trusted Access for Cyber” flow.
> We also plan to add a dedicated button in our /feedback flow for reporting false positive classifications. In the meantime, please use the "Bug" option to report issues of this type. Filing bugs in the Github issue tracker is not necessary for these issues.
What a convenient argument, you can make it fit anything
"This rerouting is related to our efforts to protect our profit margins. The $current_top_model is our most expensive model to date. It can be used as an effective tool to get semi-useful results, but it can also be exploited for using a lot of tokens which costs us money, and we take profitability seriously. When our systems detect potential excessive token generation, they reroute to a different, less-capable reasoning model. We’re continuing to tune these detection mechanisms.
In the meantime, please buy a second $200/mo subscription."
If that's the case, then their API should return an error. Billing the user while serving a response from the wrong model is a horrible outcome. I'd go as far as to say that it's borderline fraudulent.
Sounds like a thing they've said a dozen time so far about how their models are too scary. And a bad implementation of controls on top of that.
But right now I want to focus on what one of the more recent comments pointed out. "cyber-capable"? "cyber activity"? What the hell is that. Use real words.
I was wondering the same thing! Looked into it a bit, apparently 'cyber-capable' is defined by lawmakers in 10 USC § 398a:
> The term “cyber capability” means a device or computer program, including any combination of software, firmware, or hardware, designed to create an effect in or through cyberspace.
So apparently, OpenAI's response is written by and for an audience of lawyers / government wonks which differs greatly from the actual user-base who tend to be technical experts rather than policy nerds. Echoes of SOC2 being written by accountants, but advertised as if it's an audit of computer security.
No, this is incredibly naive. It's all about more biometrics and PII for sama [0]. Zero chance that Google (of all places) and Anthropic's lawyers would somehow take a wildly different stance, or as a company be that much chummier with US gov, than OpenAI.
It has been more than a year since ClosedAI started gating API use behind Persona identity checks. At the time I was told by numerous HNers "soon all of them will". We're now many model releases later and not a single other LLM provider has implemented it. There's only one conclusion to draw, and it's not that they care more about what their lawyers are supposedly saying. It would be absurd anyway given that they well know how the current US Gov operates. Grok made a CP generator publically available on a platform with hundreds of millions of users, US Gov doesn't care. Understandable, given recent revelations they were almost surely actively using it themselves.
What does it mean to detect "potential cyber activity"? Apparently nearly 9% of the users of GPT-5.3-Codex were detected engaging in "cyber activities". I have no idea what "cyber activities" are, and I've been using the internet for 30 years.
When the GPT-5 router architecture was introduced I worried that OpenAI would use the technology as a pretext to mislead or defraud users by substituting in worse quality when they could get away with it and then "blame it on the AI" when they got too agressive.
I don't know if we're there yet but these reports do not fill me with hope.
The kind of "pay me premium, I am giving you non-premium" type of fraud?
It just proves that there is not much of an improvement if they can get away with, it isn't? But hey, I am sure that the benchmarks are all saying otherwise.
Today I also discovered that the speed of gpt-5.3-codex in Codex CLI is extremely slow, and then I found that response.model was routed back to gpt-5.2-2025-12-11 by the upstream.
aaaaaaand this is why i prefer anthropic. There is just too much sneaky/misleading/deceptive things with chatGPT. Even if benchmarks show codex to be slightly better, the developer experience with claude code is much better.
It would be great if the HN title could be changed to something more like, 'OpenAI requiring ID verification for access to 5.3-codex'?
> Thank you all for reporting this issue. Here's what's going on.
> This rerouting is related to our efforts to protect against cyber abuse. The gpt-5.3-codex model is our most cyber-capable reasoning model to date. It can be used as an effective tool for cyber defense applications, but it can also be exploited for malicious purposes, and we take safety seriously. When our systems detect potential cyber activity, they reroute to a different, less-capable reasoning model. We're continuing to tune these detection mechanisms. It is important for us to get this right, especially as we prepare to make gpt-5.3-codex available to API users.
> Refer to this article for additional information. You can go to chatgpt.com/cyber to verify and regain gpt-5.3-codex access. We plan to add notifications in all of our Codex surfaces (TUI, extension, app, etc.) to make users aware that they are being rerouted due to these checks and provide a link to our “Trusted Access for Cyber” flow.
> We also plan to add a dedicated button in our /feedback flow for reporting false positive classifications. In the meantime, please use the "Bug" option to report issues of this type. Filing bugs in the Github issue tracker is not necessary for these issues.
reply