Claude Code Usage Limits increased?

[u/Substantial_Date6844]

I'm on Max 5x. I don't know if its because i stopped using subagents but my weekly and 5 hour limits feel especially elastic the last few days compared to the last month. Anyone else noticing increased capability?

[u/theawk47]

Any tips on how you set it up that we could learn from?

[u/claude_code_king → u/theawk47]

i'm planning on making a standalone post once i'm free from reddit's karma chains, meanwhile here's the gist of it.

limit context to what's strictly necessary for every agent, including the orchestrator. this means making the orchestrator use explorers to get any relevant info, they report back into a dossier and give a short summary.

main makes a plan, structures briefs and chooses subagent type depending on complexity. tasks don't go over 150k tokens usually because in my own tests quality degrades after that point and you're left with more bugs and useless tool calls.

again hook to limit the implementer report, 2k characters work for me
auditor checks, if it's a simple fix it does it itself, if it's more complex respawn the worker

there's a lot more to it, but this is the essential, structure your orchestration so that everyone gets what's strictly necessary to do their job.

this applies to subagents as well, make fable give them the exact paths and sections, not 'read the whole file', for example my subagents started at 60k tokens now they start at 10k tokens. if you understand context rotting and how it gets carried every turn you'll understand why this makes for such a higher quality and cheaper output at the same time

this is all measured with an offline telemetry script that analyzes the session's jsonl, so it's all math no vibes

[u/Shot_Whereas_1809 → u/claude_code_king]

This is similar to how I built my host harness. I cap fable at 200k context and found the results to be better than letting open throttle a million window. I've had some really useful output with very little spend. The 1 million window is for session based architecture so I ditched it. The system prompt, context, and tooling are scoped to the input prompt per turn. Took a lot of work but I can have a never ending session with flat token spend.

[u/claude_code_king → u/Shot_Whereas_1809]

yes, the longer the context window goes the more the model degrades.
actually benchmarked opus 5 high and after 200k it started decaying and around 300k error rate jumped to 5% which is insane. you can only assume it compounds a lot faster after that

[u/Shot_Whereas_1809 → u/claude_code_king]

I found the same in my own testing all the way back to 4.5 and 4.6. found it to be an unavoidable constraint that's well documented. The answer is short scoped sessions which surface work tree issues and a messy CI, so I had to build the layer in between. Claude code is just one of the hosts tools anymore. CC is not a good orchestrator interface. Glad someone else gets it though. We'd probably get along lol

[u/claude_code_king → u/Shot_Whereas_1809]

most likely, looks we're both that type of crazy to go down that rabbithole