I’m documenting what appears to be a reproducible regression in long-running, tool-enabled ChatGPT Web “Chat” turns. ## Summary Since approximately August 20, 2026, long-running Chat turns that use tools/custom MCP/connectors have repeatedly stopped interacting with tools after about 25–26 minutes…

This issue is being discussed in this megathread. Please join us! [image] GPT-5.6 High execution regression: ordinary Chat went 102m26s -> repeated ~25–26m stops on same Plus account; Work still gets long-run handoff Bugs me too worked for 25m 53s the final …

The part of this report that adds the most independent evidence beyond the linked threads is your own healthy-MCP / recoverable-state control. If you already preserved one clean specimen, the highest-value compact record would be: plan + model/effort, turn start and stop timestamps, the exact termi…

Agreed — and after reviewing the megathread, I think your distinction is exactly the useful one. In our own Plus / GPT-5.6 Sol High setup, the recurring ~25–26m failure is not equivalent to the MCP process dying: the gateway remains externally reachable, and a fresh normal-Chat turn can reconnect t…

Thanks — I’ve gone through the megathread. The newer evidence there is useful because it narrows the issue: this looks less like a universal 25-minute hard cap and more like heterogeneous execution/routing. Some ordinary-Chat GPT-5.6 High turns get the long `conversation-turn`/worker path and run >4…

If “High” can still run for 100+ minutes, then what changed around Aug 20 that made so many normal chats start getting cut short? And why are users the ones having to piece this together instead of being told?

That is now the central question, but the new evidence lets us narrow it a little. On my account the Aug 20 change is not just a remembered quality drop: the preserved native data brackets an observable switch from the old durable worker/SAServer family to the shorter foreground-style path. What we…

Thanks, this actually clears up a lot. If the 100+ minute durable path still exists, then yeah, it clearly wasn’t just globally removed after Aug 20. What bothers me most is exactly the part users can’t see: why one chat gets admitted to that longer path and another one with the same model / reason…

They were given three options, A,B or C to answer, they chose not to. Yet they are active elsewhere daily. Support doesn’t reply to my emails either… If you have managed to get actual engineering contact before, it would help tremendously.

Correction to my shorthand in #9, because the exact Support history matters. The AI-assisted Support surface did answer my earlier 1/2/3 routing question: it replied “3. CANNOT ROUTE” and said that surface had no mechanism or authority to perform the requested product/engineering routing action. I…

Unfortunately no, I havent managed to reach engineering directly either. If you couldnt with this much technical evidence, I doubt I would have better luck. I have only had support level contact so far. :melting_face: It honestly feels no different from just opening the Help Center, unless there i…

ChatGPT Web tool-enabled turns regress to ~25–26 min since Aug 20; Work lacks custom MCP

ChatGPT Bugs

rabbitdaisuke September 14, 2026, 8:24am 2

This issue is being discussed in this megathread. Please join us!

Topic		Replies	Views
GPT-5.6 High execution regression: ordinary Chat went 102m26s -> repeated ~25–26m stops on same Plus account; Work still gets long-run handoff Bugs chatgpt , bug , conversation , regression , 5.6	208	7717	October 6, 2026
GPT-5.6 Sol has seriously deteriorated the past week or so Bugs chatgpt	21	1324	October 11, 2026
ChatGPT wont get any work done after the 19th Outage Bugs chatgpt	20	2053	September 10, 2026
Custom MCP connector disappears after successful invocation in Chrome Web Chat and Desktop Chat — no second request reaches MCP server Bugs bug , mcp , apps-sdk	18	752	October 5, 2026
Before Astra Launches: Please Acknowledge and Fix the GPT-5.6 Long-Context, File, Thinking, and Reliability Regressions Affecting Paying Users Bugs chatgpt , api , bugs , 5.6 , astra	23	1886	September 7, 2026

ChatGPT Web tool-enabled turns regress to ~25–26 min since Aug 20; Work lacks custom MCP

Related topics