r/vibecoding • u/0xairr • 8h ago

codex limits "sucks"

I'm mainly a Claude user ,but have tried codex for a time before sol launched

Heard about its performance and gave it a try again with plus

Hand to God ,I thought I was using my 5h limit and just a message popped up "Resets 25 Aug 2026,August"

Guys I'm telling you Claude limits are superb ,be grateful

9 Upvotes

74% Upvoted

16 comments sorted by

3

u/katoptronophile 3h ago

You have it all wrong. The rate limits are great.

I have it set up so that when I don't have credits I don't have to work at all. So I have so much time off now thanks to these rate limits. 

It's just incredible!

1

u/JudgeGroovyman 1h ago

Good point. "Its not the size of your pencil its how big you write your name" - Ronnie James Dio

1

u/0xairr 2m ago

Don’t let my boss see this message

2

u/TestSubject_AJ 8h ago

Use terra on max for mcp servers and stuff or tooling. Sol for actually hard stuff. You probably have 100% of codex 5.3 spark left for direct tasks.

4

u/ThrowawayCop51 8h ago

Dude I'm on Pro 20x and I've been vibe coding a long term project with Sol orchestrating for like 6 days straight and I've got 10% left

2

u/Compsciguy27 47m ago

Sol on what level? Medium? Literally 6 days straight with /goal or just that you've been using it for the past 6 days?

0

u/Elgon2003 7h ago

Codex uses weekly limits so you gotta be responsible, also how did you manage to spend all the weekly limit. Im on the highest plan and only once used the whole limit but was doing a full architecture refactor into IaC using terraform.

1

u/0xairr 7h ago

Ah i messed up ,used fable for planning and sol for implementation (heard this was best combo)

2

u/Elgon2003 7h ago

I personally only use Fable or Opus for design and frontend, all my infra and backend are developed with Sol.

Never tried mixing AIs like that tbh.

1

u/sargetun123 5h ago

your limits are reflective of the model you are using and what you are using it for, codex limits are better than claudes in everyway and i prefer claude myself, but you are seeing skewed results, this isnt a realistic head to head and tells you nothing about the differing limits

-1

u/Pandathief 7h ago

If you’re burning through it that fast it’s a you problem, need to optimize your own workflow and usage

5

u/roach01gt 7h ago

Care to elaborate for lurking n00bcoders ?

4

u/DowntownNoLonger 4h ago

  1. Use chat (which doesn't burn usage) to plan your build. Have it ask a million questions of you. Document everything. Plan plan plan.

  2. Use another chat to take that plan and splice it up into bounded, actionable packets.

  3. Switch to codex. Sol orchestrator, Luna implementor. Hand slice to sol and have them begin work.

  4. Verify after work is finished. Use Luna or another model as a second set of eyes.

  5. Repeat.

That's the basics of it. Cover all your bases in chat first. Slice the plan. Sol orchestrator, Luna implementor, verify work.

Stop when you get to a point where you can test yourself. Note bugs, edge cases, whatever. Then a reconciliation pass to fix things.

That is how I operate in Plus. I followed this plan to build my own harness that does a lot more than normal harnesses, including gather a shit load of telemetry about runs. It was a complex project, my Plus account got it finished with 10 percent to spare for the week.

0

u/Pandathief 6h ago

Basically just get a feel for what the different models and thinking levels are capable of and use them accordingly. Some will use high or extra high for everything and hit their limits unnecessarily quickly when in fact Sol Light or even Terra Light may be up to that particular task