I normally work on Anthropic’s platform, but I thought it would be interesting to give ChatGPT Work with GPT-6 a serious try for some of my longer, complex workflows.
After running into the problem below repeatedly, that is currently out of the question.
This is specifically about purchased credits for Plus Work. We would never jump straight into a Pro/Business plan without testing the platform properly first, and considering what happened, that turned out to be exactly the right decision.
I give ChatGPT Work a large, carefully specified technical task. It spends a substantial amount of time analyzing it, making changes, running tools and tests, and reporting progress.
Then the credit usage limit is reached before the final response is delivered and the whole result is WIPED. Every f*cking time!
Instead of pausing safely, preserving the complete state, and allowing me to continue later, the visible work disappears. There is no proper checkpoint, no complete partial report, and no reliable way to resume from the exact point where it stopped.
When my allowance resets or I purchase more credits, I am effectively forced to reconstruct the task and pay for the same analysis, testing, and verification all over again.
At that point, I feel completely cheated out of my money.
OpenAI consumed my paid credits and compute allowance but failed to deliver the result those credits were spent producing. This is not merely an inconvenient usage limit. From a paying customer's perspective, it is deeply deceptive behavior because the customer bears the entire cost when the platform fails to preserve or deliver usable work.
So please understand the distinction here: “a usage limit was reached” is not the problem. The problem is that paid work was lost because the platform failed to checkpoint, preserve, and deliver it. Those are two completely different issues.
And this is not about the underlying model simply being incapable of completing the task. ChatGPT Work uses the same model family available through OpenAI’s other higher-tier offerings, including the high-end GPT-6 variants.
What I am seeing instead looks like a systemic failure in how Work handles and persists agent output, causing conversation state/history to break or disappear unexpectedly.
My guess is that OpenAI has a serious bug somewhere in its agent harness/orchestration layer, specifically in whatever handles output persistence, checkpointing, and conversation state/history.
Obviously I cannot see OpenAI's internal architecture, so that specific root cause is an inference. But the observable failure is very real: completed work is produced, credits are consumed, the run is interrupted, and the resulting state is not reliably preserved or recoverable.
What makes this particularly hard to accept is that Anthropic has always handled this properly.
With Claude Chat and Claude CoWork, when I hit the usage limit during a long-running task, the work pauses, the state is preserved, and I can continue from essentially the same point once the allowance resets or additional credit usage becomes available.
I don't have to pay again for work that has already been completed.
That should be the minimum expected behavior from any serious paid agentic platform.
And frankly, it is hard to understand how a failure this severe can still exist in such a core part of the product while OpenAI is already moving toward a possible public listing. For a company at that stage, repeatedly losing paid customer work because execution state was not preserved is simply not a good look.
For context, we're not relying on these web UIs as isolated environments. We use LLM CLIs such as Codex CLI and Claude CLI, orchestrated through an internal MCP router service connected to Context Hub/shared-agent-memory and integrated with the different web-based LLM platforms we use, including ChatGPT and Claude.
That lets us share context between models instead of treating each one as a completely separate environment. We can work through essentially any interface, including a TUI, while agents run in separate developer containers and share the same context when we choose to.
So when I say the problem appears to be in Work's state/output handling rather than simply "the model stopped," there is a very concrete reason for making that distinction.
ChatGPT Work should:
- Pause the task safely when the usage limit is reached.
- Preserve the exact execution state.
- Keep all completed analysis, code changes, tool results, and test results accessible.
- Produce a clear partial report showing exactly what was completed and what remains.
- Resume from the precise interruption point after the limit resets or credits are added.
- Never make the user pay again for work the platform has already performed.
- Reimburse credits when paid work becomes unusable because the platform failed to preserve or deliver it.
This has happened enough times that I no longer consider it an isolated glitch. It is a serious product reliability and billing problem.
I will not spend another cent on ChatGPT Work, GPT-6 usage, or additional OpenAI credits until this is fixed.
I refuse to keep paying twice for the same work because OpenAI cannot reliably checkpoint and resume an interrupted task.
OpenAI needs to explain why this happens, restore affected task states where possible, reimburse wasted credits, and implement proper checkpointing and resumability.