ChatGPT Pro - Pro - Temporarily Limited. Contact Support

Coding with ChatGPT
,
1

So here is the limit with GPT-5 Pro. I was troubleshooting code, you can look at my account and see my previous thread Comparing GPT-5 Pro and earlier LLMs for developers - Coding with ChatGPT - OpenAI Developer Community

I called it garbage performance but someone renamed my thread, so be it.

While troubleshooting my code, I suddenly noticed my model was swapped to THINKING from Pro, so I went to change it, but the Pro area is greyed out and asking me to contact support.

image
image850Ă—591 22.2 KB

  1. I am not using VPN
  2. I Am sole user of my account
  3. I am working on my own project not anyone else’s
  4. I have been pro user for months now and have previously had regular GPT-4 produce 2000 lines of code for me a year ago, whereas now I think the model was programmed to flag that as abusive, despite my current code is far less than that.
  5. I have not done any “programmatic or automatic extractions” I only asked for the code to be fixed.
  6. Garbage code that GPT-5 Pro provides leads to additional unnecessary prompts, and I assume that is now being flagged as abusive. Each new thread can output a maximum of 1-3 large code dumps after that it completely plateaus and becomes gemini-level of intelligence. Now, you also get “limited.”

They have quietly released this here GPT-5 in ChatGPT | OpenAI Help Center and it reads the following:

The ChatGPT Team and Pro plans offers unlimited access to our GPT-5 models, subject to abuse guardrails. Usage must adhere to our Terms of Use, which prohibits, among other things:

Abusive usage, such as automatically or programmatically extracting data.

Sharing your account credentials or making your account available to anyone else.

Reselling access or using ChatGPT to power third-party services.

We have guardrails in place to help prevent misuse and are always working to improve our systems. This may occasionally involve a temporary restriction on your usage. We will inform you when this happens, and if you think this might be a mistake, please don’t hesitate to reach out to our support team. If policy-violating behavior is not found, your access will be restored.

ChatGPT is a great tool, but I have feared this would have happened sooner or later even for Pro accounts, I have spent over a $1000 now to have access to chatgpt over the years maybe more, and it has been a good ride, but I cannot wait until competition catches up. If I do not regain access to Pro there will be no point to renew my $200 subscription, the only reason I pay this much is to have access to Pro.

We absolutely cannot allow this to be normalized, in all my years of using GPT I was never “limited” unless I hit a use cap, for which I got PRO, and my use case did not change in absolutely any way, it’s either coding or conversations, conversations are garbage now, and so is coding, but now on top of these things, you get limited.

That limitation feels arbitrary, opaque, and user-hostile.

8 Likes
2

Same here. They restored my access, but this event made me seriously consider switching to another.

2 Likes
3

Just received the most generic response from Allan the tech support. It was literally a copy pasted first response I got from AI tech support. I requested human. Got the same exact response.

Recommendation is to wait for the “cooldown” — to which I responded, “this sounds like this is tied to usage rather than credentials if we are talking cooldown, if I shared my credentials you’d outright ban me”

I also requested transparency and actual reason why this happened, I reassured him I did not breach anything and if I have to tell me what it is and why its suddenly a problem for about 200 people on Reddit as well those who bothered to make a post or comment or like it.

1 Like
4

I checked last night and my access was restored as well.

Yes, same here, this has left a REALLY bad taste in my mouth and has significantly eroded my trust in their service.

1 Like
5

I had a similar experience with openAI working with images. I suddenly reached an arbitrary limit and my project was abruptly halted for a cooldown. While I understand the need for guardrails on monthly accounts when usage goes beyond predictions, in most cases, I would hardly call it abuse. Most users will have been surprised by not being able to complete what they thought was legitimate work and in no way were trying to game the system.

My suggestions to OpenAI, which may or may not have been heard were, first, to notify the user of an impending limit so they can plan ahead, and not have their project come to a screeching halt in an unpredictable manner. Second, give options to work around the issue. For instance, once a plan’s limit is reached, a per transaction price should be offered. While not as economical for the user, let’s face it, too many transactions is what triggered the stop, and a per transaction price during the cooldown is a reasonable compromise for both parties.

The idea of a sudden cooldown with no workaround does irreparable damage to user confidence and must be addressed by openAI or current and prospective users will consider unpredicted cooldown interruptions to projects as a risk factor to be compared with competitors.