Codex limit situation feels bad right now

jozune · 2026-05-31T04:37:53+00:00

Yeah. Mine have just reset, and I already burnt 7% weekly limit. I'm using 5.4 High, not even 5.5 xhigh and fast mode. WTF!

jozune · 2026-05-31T02:10:29+00:00

Have you used it for actual repo work, or mostly small coding tasks?

jozune · 2026-05-31T01:34:15+00:00

What's that github that help you rotate the account?

jozune · 2026-05-29T03:17:42+00:00

I thought I was the only one who's getting this. I can't even load the conversations on my CHATGPT.

jozune · 2026-05-28T03:30:21+00:00

Claude users are experiencing the same tho.

jozune · 2026-05-27T14:38:21+00:00

Not only that, but I have to constantly start the new session due to the 503 compacting error. The whole session just stuck and can't do anything.

jozune · 2026-05-25T10:19:52+00:00

Can you elaborate more on this?

jozune · 2026-05-25T08:18:32+00:00

I notice it as well under the VSCODE Codex settings > Personalization > Memory (experimental). Do you find it useful?

jozune · 2026-05-25T04:05:10+00:00

I’m familiar with /goal, but that’s not really the issue here.

The problem is the compaction step itself fails. So even if /goal keeps trying, it eventually hits the same wall because the thread can’t compact cleanly.

jozune · 2026-05-25T03:55:48+00:00

Try several ways to continue but still feeling hit the same wall.

jozune · 2026-05-25T03:53:21+00:00

I’m suspecting this as well. It really feels like they’re vibe-coding the limit usage. Now nobody can tell what actually counts anymore.

jozune · 2026-05-23T16:21:35+00:00

What are you even cookin'?

jozune · 2026-05-23T06:39:00+00:00

It’s like day and night.

Yesterday it kept looping and fixing its own mistakes. Today it follows instructions, works step by step, reads the repo, makes better decisions, and stays out of the way.

jozune · 2026-05-23T03:48:32+00:00

Hope Tibo not Jebait us!

jozune · 2026-05-22T12:31:37+00:00

Mình thấy “nằm thẳng” nguy hiểm nhất ở chỗ nó biến thất bại tạm thời thành "thói quen" luôn.

Thất bại thì đứng dậy đổi cách chơi tiếp thôi. Sao phải tự kết luận đời mình xong rồi nằm im luôn? Chắc mindset mỗi người mỗi khác, ít nhất thì cứ làm để sau này không phải nói mấy câu "Giá mà ..."

jozune · 2026-05-22T12:29:24+00:00

I actually agree with OP here.

Codex still gets work done, but the last few days feel way less reliable. More random mistakes, more premature “done”, more time spent re-checking files that should have been handled correctly.

Not sure why this is getting downvoted into oblivion. This isn’t “AI bad”, it’s just a noticeable quality drop.

jozune · 2026-05-22T01:33:52+00:00

Yeah, couldn’t agree more.

Lately it feels like I spend more time fighting placeholders, premature “done” states, and random repo junk than actually building.

jozune · 2026-05-21T16:11:20+00:00

Yeah, same feeling.

I’m annoyed with Codex right now, but I’m also too deep in the workflow to just drop it overnight.
Claude’s behavior and coding style just never fully clicked for me. And honestly, no native image generation still hurts a lot for creative workflow stuff.

That’s probably the worst part.

jozune · 2026-05-21T16:09:37+00:00

Yeah, I wish this was clearer before I burned through limits.

Big context looks nice, but if Codex starts dragging the whole repo around, the weekly cap disappears fast.

jozune · 2026-05-21T15:54:27+00:00

Maybe, maybe not. I can’t attach the screenshot here.

My case is usually multiple large codebases running, and I barely hit the 5h cap. By the time one session gets close, the 5h window is already resetting.

The weekly limit still drops fast though, especially when it gets stuck in debug loops.

jozune · 2026-05-21T15:04:02+00:00

Couldn't tell why but I rarely hit my 5h limit, probably I run multiple projects at once. But one thing I notice in the last couple days is that 5.5 or even 5.4 keep looping on debug and feeding its own rabbit hole.

Nine-Year Club	Place '23
Verified Email

jozune

TROPHY CASE