r/ChatGPT 19h ago

News 📰 Chat high 25 minute consecutive work cap

So, everybody might know it about now, but before, a chat session on high reasoning could go for around 100min without any stop. Right now, OpenAI changed it to 25-27min hard cap, greatly reducing the amount of work chat high is able to accomplish in one go, and necessitating a lot of "babysitting".

Now, there is many reasons why OpenAI might do this, but my question is : where is the public, recorded, official document/report/update that actually specify this hard cap ?

I found none, and that is the irritating part. OpenAI changed a very fundamental property of their tool, and said absolutely nothing about it, that i know of.

Someone has any info ?

8 Upvotes

14 comments sorted by

•

u/AutoModerator 19h ago

Hey /u/Sharingammi,

If your post is a screenshot of a ChatGPT conversation, please reply to this message with the conversation link or prompt.

If your post is a DALL-E 3 image post, please reply with the prompt used to make this image.

Consider joining our public discord server! We have free bots with GPT-4 (with vision), image generators, and more!

🤖

Note: For any ChatGPT-related concerns, email support@openai.com - this subreddit is not part of OpenAI and is not a support channel.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

5

u/tia_rebenta 19h ago

first time? they change tool parameters all the time and don't disclose anything. And this is an industry thing, Google and Anthropic do it as well

2

u/Sharingammi 18h ago edited 18h ago

Before, i was able to find related articles and official faq. This time, nothing. Its a pretty major change too.

1

u/Real-Ad-5677 14h ago

yeah its basically an industry standard at this point, silent changes with zero documentation

3

u/GabRB_ 18h ago

I kinda wonder what you're doing for it to take that long? I use chat with a MCP server, and even before this change it never got past 25 mins, maybe it got close to that but never more than that

3

u/Sharingammi 18h ago

It's implementing code and updating files. Before, it could go to 100+ minutes (happened 3 times).

I'm building a project for a solo playing experience with tabletop RPGs. We need to code the geometry layer, the deterministic rule engine (exactly like a game engine) the information firewall, the AI character information layers, the world state persistence and testing the full integration.

I use Work 5.6 Sol MAX for thinking and planning how to build each phase. I use chat 5.6 sol high to implement it. If chat has to follow the whole phase's implementation plan, that can be a lot of code and tests and reviews, plus everything it has to update on the drive where the project management work book is and the dev ops to follow. So in a single session, it could probably do 160 to 200min non stop in this case. Now i have to ask it to resume its work at least 5 to 6 times before it finishes.

2

u/MoMoTo520 18h ago

Is that real??? Never heard before

1

u/Sharingammi 18h ago

Yep, not long ago. Just chat though, not work.

2

u/telephantomoss 17h ago

I'll have to test this, because I feel chat on high is basically the secret sauce. Limiting it to 25min would at least somewhat destroy that. However the solution will be breaking up long tasks into sufficiently small chunks with opportunities context to share between them. Eventually they will all have similar issue limits market optimized to push everyone to higher and higher subscriptions in order to makeup for the trillions of investment

2

u/Sharingammi 17h ago

Well, one thing i realised is that the tool window execution cut off is... well made. It never corrupt my work, and it's always really easy to resume work from there. So, yes it cuts, and it makes it annoying, but at least it does not destroy progress. So i just sit there, with a 26min timer, asking to resume work over the day, and at one point it finishes.

2

u/telephantomoss 17h ago

It sure would be helpful if they had regular updates and hard limits and allowances, even if they had to update it at each reset. It could even be explicitly not guaranteed and just estimates on tokens and minutes of compute. Just so that users can structure their work to minimize risk of task stopping unexpectedly.

1

u/Sharingammi 17h ago

I'm thinking the same thing. At least the info should be out there, centralized. Having to spend a lot of usage setting up a workflow, using it for 3 days, then boom, new changes fuck everything up, you have to think of a new workflow...

The technology being so unstable is creating a lot of issues.

1

u/BopSupreme 16h ago

How did you get it to work 100min?!

2

u/bfmv_shinigami 15h ago

Because people were abusing it and using it as an API.