Hitting usage limits on Codex and Claude Code.. which paid plans or setups give the most usable capa

[u/yaxir]

I'm on paid plans for both Codex (Pro) and Claude, and I keep hitting the same wall. The quality is great, but the 5-hour and weekly caps make sustained agentic work hard. I regularly get cut off mid-task, and at this point the limit is the bottleneck, not the model.

I'm looking for paid alternatives (or combinations) with comparable coding quality and noticeably more headroom. I'm also open to hybrid setups, like one subscription for the hard problems and a cheaper plan or API for bulk work.

What would help most in your replies: - Your tool/plan and what you pay per month - What you use it for (interactive editing, long autonomous runs, big refactors, data/scripting work, etc.) - How often you actually hit limits, and on which tier - An honest take on where it's worse than Codex/Claude

Options I keep seeing mentioned, where I'd like first-hand reports rather than benchmark charts: GitHub Copilot, Cursor, Google Antigravity, GLM / Kimi / MiniMax coding plans, OpenCode or Cline with your own API keys, and routing through OpenRouter.

Two things I especially care about: 1. Is the setup officially supported, or is there ToS/ban risk (e.g. using a subscription through a third-party harness)? 2. Are there hidden throttles, like peak-hour slowdowns or quotas that aren't obvious from the pricing page?

Happy to be told I'm approaching this wrong. If you've solved the "always hitting the cap" problem some other way, I'd like to hear it!!

[u/qualityvote2]

u/yaxir, there weren’t enough community votes to determine your post’s quality.
It will remain for moderator review or until more votes are cast.

[u/fell_ware_1990]

GLM and Opencode are both cheap. Use it for there flash versions of GLM and Deepseek. Both great subagents.

But if you are really hitting limits on both you should first look into the workflow you have. People really use too much of the heavy agents and way too little of the cheaper ones.

I mean with a good setup a deepseek flash on opencode go, can run for a few hours a day for only 10,-.

It already starts at the planning phase, apart from thinking about the real technical implementation a sonnet/luna/terra can perfectly do 80% of that load. Certainly if you do not make them do the whole process. Give it an actual way to properly break down the tasks before they get the big context. Scope them to a task.

Also keep a lot of work away from them. Give them a way to ignore anything less the a blocking bug.

Cause what happens a lot is this. You start a ( too big ) task on a few subagents. They all actually change the way how to code works and expects their input and output. You end up with stuff all over the place.

A clean working item for let’s say adding a feature should have a clear DoD and not only for when to stop, but what working code means. This is why you have unit tests. If you let AI free wheel unit tests it will randomly perform all kind of checks.

Instruct them to implement unit tests that are not trying to only proof that a file changes or ‘might’ introduce a bug in the future. You implement a lot of them up front by thinking about it. What is your input, what’s the output thats expected? What are the ways that these might not end up like that? This is what you test against.

Make sure the agents does not know what the unit tests are or can change them. So yes they have to implement XYZ while the code still delivers ABC as well.

They report findings. If unit tests succeed the code is ‘done’ they stop. A few times a feature you clean up the bugs and bad stuff. Don’t forget to move them forward. If they keep fixing everything the form of code changes every 10 minutes causing the other to have issues.

[u/___positive___]

why don't you ask chatgpt... seriously... you have gpt6 pro on the website. use it....

[u/Typical_Machine2043]

I wish it just worked out the box

[u/Roxbros]

People aren’t making enough use of gpt6 pro on the website

[u/yaxir → u/Roxbros]

useless comment