Replies dated this day in the collected sample: 79. Collected since 5 Oct 2026: 1457.
X replies are found by search and each one is checked against its public post on X. Last read: 26 Oct 2026, 23:46 UTC. Not every reply is read.
- A problem
Keep getting "Error running remote compact task" for the past few days - it is essentially unusable
@lihua_lau on X ↗ · 00:12 UTC
- A problem
Too many errors on agent spawn using dot. Is everything okay? Work chat also stuck with no response, stop and send message doesn't help
@Danonika1 on X ↗ · 00:32 UTC
- Mixed
I didn’t say reset the usage! Need that shit banked for actual emergencies 😭 Hmm maybe a little side bank would be nice tho 😉
@porterwonghk on X ↗ · 00:59 UTC
- A problem
Lol, same. Codex just added 150gb+ to my disk today. Still tracking down why..
@OneStoryRoad on X ↗ · 01:31 UTC
- A problem
Pro 500 user here. I still didn't get my reset.
@Mario2rjv on X ↗ · 02:27 UTC
- A win
Makes sense. I’ve been using the 80–90% context threshold as a hard trigger, but the “agent re-reading files it already saw” signal is more practical mid-task. For long-running projects I’m now combining both: force a file handoff at major milestones, and also reset earlier if I…
@RandyJinAI on X ↗ · 02:28 UTC
- A problem
The context says it has more room but still compacts at somewhere just over 50%. And before it compacted at just under 100%. Hardly any difference
@danielpopovallw on X ↗ · 02:40 UTC
- A problem
I built my own compaction software to deal with that. My .codex chats filled up a terabyte of hard drive space it was insane. However for all the inactive chats that were not pinned and were also more than two weeks old the only thing I cared about saving from them was the…
@DeathStarRobot on X ↗ · 03:10 UTC
- A win
Ok i was wrong this is a good default, from my very short experience.
@rhett206564 on X ↗ · 03:18 UTC
- A problem
So can it be reset tomorrow? You have reduced the weekly usage of Pro and the new model has increased in price, so I have to come and see if you can reset it.
@xying63 on X ↗ · 03:34 UTC
- A problem
thank you. i always out of disk space
@Joyortoy7 on X ↗ · 03:44 UTC
-
Selected model is at capacity. Please try a different model. What's error about 6.1-Sol ?
@CengFuming on X ↗ · 03:50 UTC
- A problem
Anybody else saw usage depleting faster since yesterday? There was a reset done and after 1hr, sol 6.1 xhigh used 10% of consumption. Normally it would consume 2-3%.
@arjunlucknauth on X ↗ · 03:56 UTC
- Mixed
I actually prefer working with Opus 5.5. It’s smarter, more creative, and more intelligent than any GPT model I’ve tried. At this point, the only thing that makes GPT worth coming back to is the occasional usage reset.
@parish_khan on X ↗ · 04:03 UTC
- A problem
I used three $200 accounts post-reset to fix a bug Astra created. I told it to find and correct its mistake, but it just looped. Woke up to the third account drained — still no fix. You ignore model smarts, cost and speed, pushing useless updates. That’s GPT for you
@shijkyou on X ↗ · 04:04 UTC
- A problem
built a live codex usage tracker on an apollo WLED display and lately i’ve been seeing it go back to 100% everyday! welp we were not spoiled today and my next reset is on the 20th☹️ kicking rocks
@ohyay_eth on X ↗ · 04:07 UTC
- An idea
Can you ask the team to prioritize this issue? Currently, I have to maintain a fork with the fix since you guys don't accept PR. This can help save significant token cost for cold start. I also have another thing that will help cut down the token cost by…
@juminoz on X ↗ · 04:10 UTC
- A problem
You're optimizing disk space while sitting on a pile of garbage. As a model provider you can't even serve your own models. Capacity errors every day. Fine if it's extra capacity, but even 6.1 just says "capacity" and won't run. So what exactly am I paying for? And your TPS is…
@deshiou0604 on X ↗ · 04:15 UTC
- A problem
du -h shows ~/.codex (my old version) is using 72 MB. That's about 0.03% of my disk. - not "relevant for most codex/work users", so are you going to reset us or reneg?
@AccordingToSamu on X ↗ · 04:15 UTC
- Mixed
If this does what I think it will do, I will absolutely love this update. I have to clear my disk space up about twice a day when I have the codex running!
@brad_amor on X ↗ · 04:29 UTC
- A problem
I am really tired of you guys. Never seen such an unstable system. One day in 4 hours the entire usage is consumed, the other day it feels like 10x usage and you can't consume it. Then the speed is like fantastic, yesterday 1 hour for one task. FUCK YOU
@Nalfur on X ↗ · 04:39 UTC
-
Hoping the fixes to this will be one of the goalposts: Error: OpenAI Responses stream ended before a terminal response event
@scidius on X ↗ · 04:39 UTC
- A problem
While your at it, maybe look at why Codex takes 6G+ of memory for basically nothing a ruins a 32G laptop.
@R2Jules on X ↗ · 04:48 UTC
- A problem
What's the matter recently? Not only does it suggest that the model has insufficient capacity, but it is also super slow.
@MengFan786110 on X ↗ · 04:49 UTC
- A problem
Yesterday’s reset never even came in
@dotcomanto on X ↗ · 04:55 UTC
- A problem
Are you serious? Codex was barely functioning properly all day and your idea is files now take up less space on the drive? I can do it myself. It's called deleting unnecessary files Can we finally get some meaningful optimizations? Because this sounds like a reset
@DreamWade on X ↗ · 05:08 UTC
- A problem
I'm sorry but as much as I might like my drive space, this is simply horrible. I just hope the data stored in rollouts and databases is intact. As for calling it worthy of a "28 Tibo Days"... That's... quite embarrassing. If that continues, we'll get a resignation letter at 28th
@TajemnikTV on X ↗ · 05:10 UTC
- Mixed
Please Tibo, review the weekly limit for Plus and Business subscriptions; it was used up in two days with normal use. Apart from that, SOL has been terribly slow in the last few days.
@gaxupin on X ↗ · 05:14 UTC
- A win
My reset was used to optimize shader computations and gave me 254% FPS increase on the side. I need another one to continue further 😅
@rzvwolf on X ↗ · 05:18 UTC
- A problem
ready for another reset for babysitting all the capacity errors
@JacobRothfield on X ↗ · 05:25 UTC
- A problem
When using Codex, frequent file scanning in a huge project directory spawns rg.exe, driving CPU usage to ~90% and causing system lag. The root cause is selecting an over‑large project folder. Is this issue on GPT’s fix roadmap?
@noranodea on X ↗ · 05:26 UTC
- A problem
see this shit , stupid, slow, and full of bug wtf.
@mashirobbb on X ↗ · 05:28 UTC
- A problem
Crazy how they've convinced almost everyone that these resets are gifts when users are paying $200 already... for a garbage codex model that will get halved in usage at the end of October If it's this terribly slow now & usage get drained in 1-2 days, imagine at halving date.
@0xZeroG on X ↗ · 05:33 UTC
- A problem
Either reset our usage limits or fix whatever is making the model dumber and so painfully verbose.
@hopeloop179368 on X ↗ · 05:38 UTC
- An idea
Love seeing disk usage get attention. A storage breakdown for chat history, attachments and caches would make this even more useful, especially with a clear way to reclaim space without losing conversations.
@BkashJosi on X ↗ · 05:42 UTC
- Mixed
meanwhile antigravity behaves like you have all of GCP to store💀 3x more files and folders in Codex for a 1/3 of the size in AG@fhinkel @OfficialLoganK are probably working on this already
@v79842 on X ↗ · 05:46 UTC
- An idea
Great update! Could you also look into the memory leak issue? When the app is left open for a long time, memory usage grows exponentially. It looks very similar to what's being discussed in this issue.
@justin260907 on X ↗ · 05:50 UTC
- A problem
I do wander, is the app as unusable as it was when I left? You don’t seem to care about performance. I remember how long it takes to launch and the freezes it subjected my computer to. Claude never freezes
@nicitsmelol on X ↗ · 05:51 UTC
- A problem
Tibo - I thought DOTS COULD JUST KEEPIN DOTTIN THE PLACE UP?!?! "“You’ve hit the preview limit." ???? 💠💠💠💠💠💠
@BBallard2 on X ↗ · 06:28 UTC
-
Error: Our servers are currently overloaded. Please try again later. x2
@scidius on X ↗ · 06:38 UTC
- A problem
After this reset was useless to me, as I still had full usage, Codex spent the whole weekly limit trying to get a VM running. Seriously?
@DaniDebatte on X ↗ · 07:03 UTC
- A problem
"exceeded retry limit, last status: 429 Too Many Requests" anyone?
@d3muj4 on X ↗ · 07:09 UTC
- A problem
why does 'selected model is at capacity' completely stop the session instead of automatically waiting for capacity to become available and then resuming, just like it does when you hit usage limits?
@isandotart on X ↗ · 07:27 UTC
- Mixed
- Resets: every two days! - Hit model capacity: every two minutes! *State of codex 28 days challenge! 🤭
@thesturag on X ↗ · 08:01 UTC
- A problem
I was running out of space. 20 gb used by chatgpt.
@hackscorpio on X ↗ · 08:06 UTC
- A problem
Could we first address the issue of "The selected model is at capacity. Please try a different model."? Your users can't even use the system properly anymore. Why are you still trying to make further improvements? Please note the priority.
@ShaoNiannvl on X ↗ · 08:50 UTC
- A problem
Didnt got any reset neither real nor banked one...
@Schaltfehler on X ↗ · 08:59 UTC
- A win
already finished the whole weekly reset in 14h ✌️🤣😂 please another reset in 2 days im finished with my Projekt
@VitjaInnovates on X ↗ · 09:07 UTC
- Mixed
Thanks for the fix, but this was you some days ago. Now you launch a fix for "power users running out of disk space" I run Codex 24-7 and never ran out of space... So either powers users are a different thing than regular users, or IDK. Anyway... Your words from the other day…
@tasarren on X ↗ · 09:25 UTC
- An idea
A quick fix would be Wait & Retry if model is at capacity instead of simply stopping the run. That's something you can do @thsottiaux and what will make the problems for users a bit smaller. People want their Codex to work through night, not to stop 1 hour after they went to bed.
@R4mboX87 on X ↗ · 09:26 UTC
- A problem
I didn’t get a reset yesterday 🤷
@bgoldj87 on X ↗ · 12:58 UTC
- A problem
No need! I still can't utilise previous one!
@brat002 on X ↗ · 13:21 UTC
- A problem
Started seeing a lot of 429 on the pro 200 plan today
@RongduanZhu on X ↗ · 13:33 UTC
- A problem
no reset here still and still hitting bugs
@andrewbonar on X ↗ · 14:36 UTC
-
Error: Codex error event: Our servers are currently overloaded. Please try again later. (code=server_is_overloaded)
@hqb1114 on X ↗ · 14:52 UTC
- A problem
Today's Codex service stability is extremely poor, with continuous timeout reconnections. Even requests that do not time out have extremely slow response speeds, resulting in hours of wasted time. The Codex is nearly unusable; we need to fix it immediately. Thank you.
@FosenHai on X ↗ · 15:39 UTC
- A problem
Hello @thsottiaux, I didn't receive your Oct 11 or 13 global resets after switching to Plus. Support says: "The announcements did not specify which plans, limits or reset windows were included. Is this normal?
@areribas_ on X ↗ · 16:17 UTC
- A problem
My entire weekly usage limit was exhausted in just two hours on the ChatGPT $100 plan XD
@otter0x0 on X ↗ · 16:19 UTC
- A problem
Never received this reset or the one before it
@ji1902 on X ↗ · 16:28 UTC
- A problem
I didn't get any reset :/
@Ibrahim57039235 on X ↗ · 16:29 UTC
- A problem
Paying for ChatGPT Pro, but my Codex project is stuck before it can run even a read command: “exec-server rejected request (-32603): helper_unknown_error: setup refresh had errors”. Restarting the app didn’t help. @OpenAI, how do I fix this?
@Fenesyyy on X ↗ · 16:54 UTC
- A problem
Hey @thsottiaux, looks like the global reset didn’t reach my Pro account. Still at 0% remaining and using credits. Is it still rolling out?
@hburaktasyurek on X ↗ · 17:44 UTC
- A problem
My usage is already used up
@andrew2174001 on X ↗ · 18:01 UTC
- A problem
in the end, 2 days later I didn't get a bank reset and had to use a previously banked reset
@naturalSmartnes on X ↗ · 18:38 UTC
- A problem
When will these optimizations take effect? I’m not seeing it yet. Definitely using a ton of disk space
@hantla on X ↗ · 20:00 UTC
- A win
Huge!!! Disk space is a real problem with codex. It takes to many GB of useless files and things so great feature!
@sebasfernandezg on X ↗ · 20:14 UTC
- A problem
Unrelated(?) but, on Pro, I just lost like 35% of my weekly usage between closing my laptop, driving an hour, and checking back in. It would be great if I could see what's eating my usage so fast... I went from about 50% to 11% in no time at all and accomplished nothing... ugh.
@RWCantel on X ↗ · 21:09 UTC
- Mixed
Yeah I had 20GB stored just from proofs for more natural apple item hand gripping for my pose and animation editor xD
@siryeshe on X ↗ · 21:47 UTC
- A problem
I was running out of disk space
@AlbertBuchard on X ↗ · 22:15 UTC
- A problem
Adoraria terminar um desenvolvimento ao longo dos 30 dias !!! Work devora tokens … para criar um executável de uma aplicação que criei, levou 20h e 3 recargas de 5h para criar um exe para um app minúsculo
@andrecolombo on X ↗ · 22:19 UTC
- An idea
What about you give us the button to purchase ourselves ? Even better, give the button, a price and bring back the 5h limit + usage x2
@realowg on X ↗ · 22:27 UTC
- A problem
Can you optimize the memory usage of codex? It took so much space to run.
@54fby7yzwh on X ↗ · 22:43 UTC
- A win
Nice. I was having problem with disk space and this improvment happen. Thanks!! I really need this one.
@TheSetoxx on X ↗ · 23:03 UTC
- An idea
Hey @thsottiaux , could we get a slightly later reset window for Indian users? 🇮🇳 We often find out about resets at night, when we've already finished work or gone to sleep. By 9:30 AM IST, the quota has reset, leaving little time to use what's left. 1/2
@DdVgg17 on X ↗ · 23:07 UTC
- A problem
Same here! My computer is running out of disk space, and I don't have enough space to store other files.
@guo_yang14797 on X ↗ · 23:25 UTC
- Mixed
this is a decent ship, codex is the main reason im running out of space
@b96ngh on X ↗ · 23:57 UTC
3 X replies from this day are not quoted: Rantr does not have their words or held them back after automated screening. They stay on X.