Error running remote compact task: stream disconnected before completion: error sending request for url (*chatgpt.com / backend-api / codex / responses / compact )
I also use Cursor and Claude, and constant problems with Codex only.
App are extremely annoying. This isn’t the first time. It feels like I’m paying the maximum possible subscription price of over 200 euros (prices in Europe are higher) not for a professional product, but for a hack that constantly breaks. Guys, you’re not serious.
I also have been hitting this for months and months, it keeps breaking my workflow too. 20% context remaining usually and /compact just kill the session.
■Error running remote compact task: stream disconnected before completion: error sending request for url … backend-api/codex/responses/compact)
■Error running remote compact task: stream disconnected before completion: error sending request for url … backend-api/codex/responses/compact)
It’s really breaking my workflow. Each time I have to start a new session and tell the model to read the tail of the previous convo history in the .codex folder and resume. I can barely get any session that compacts more than 2 or 3 times. It’s more frequent recently. I use multiple providers, and some of them can run uninterrupted for 5 hours. This is a real issue that needs solving. Perhaps allow setting the auto compact threshold like at 40%, at least the session will keep working instead of permanently breaking every 15-30 minutes.
I’m experiencing exactly the same issue, and that chat thread just got stuck there. Force-stopping and resending the message doesn’t work. Aside from the compact API endpoint errors, the compact process is slow even under normal conditions.
Happens for me too all the time. Have been trying to change reasoning from extra high, to high, to medium but as of today i have gotten this problem 5 times in a row. Really need a solution for this.
I consistently get the following error inside the latest version of Codex app on MacOS:
Error running remote compact task: stream disconnected before completion: error sending request for url (…)
Quite annoying.
Yep me too. Feels like a serious issue since it can just torpedo a massive context.
I found you can brute force it by retrying over and over. It isn’t a good solution though for a product this expensive.
Exactly the same…
When you pay for a professional product, you expect an HTTP connection that can handle the load... I, for one, have fiber optic internet.