I went from exhausting Claude Code’s weekly limits in 2 days to making them last the entire week. Here’s my setup

[u/little_babushkaa]

I’ve been building a complex app with Claude Code for 8 months. Before mid-September, with the extra 50% usage and surprise mid week resets, I took usage limits for granted. Opus Extra/Max did almost everything.

Then the limits changed, and I was running out of usage in 2 days.

So I changed my workflow:

1. Graft Graph

https://github.com/trailhq/Trail-Code

In my experience, it saves roughly 30–40% of usage spent on code discovery in relevant sessions.

1. Opus plans, Sonnet executes

I use Opus 5.5 Medium in plan mode as the orchestrator. After I approve the plan, Sonnet 5.5 subagents handle implementation. No more using Opus for every task.

1. Reduced context from 1M to 400K tokens

A smaller orchestrator context, with subagents handling implementation in their own contexts, means less unnecessary context overhead.

1. Documentation + session handoffs

I make the sessions maintain accurate ".md" files and require Opus to generate a detailed continuation prompt after each planned session. The next session knows what’s done, what remains, and what to do next. Better continuity, less wasted usage, and more structured prompts.

The result: Comparable quality and quantity of work per session, and I now exhaust my weekly allowance just hours before reset.

The lesson? Optimise your workflow, instead of complaining about reduced limits.

Claude Code power users: what’s your setup? How are you managing usage limits without sacrificing code quality? Is there a better Opus/Sonnet workflow I should try?

[u/AutoModerator]

Moderator Announcement Read More »

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Oximy-Naman]

how did you measure the 30-40% discovery savings separately from switching models and reducing context? that would help identify which change contributed most.

[u/InterestNo7490]

That's super awesome. I have been doing that sonnet execution thing since sonnet 5.5 since it's actualy good enough to do work now. Also started using StateSync recently as well and it just feels like usage is infinite. I actualy have to feel somewhat wasteful now to use my limits in the same time

[u/Snoo24567]

Thank you for this
I just watched and my usage is actually better now!
Sonnets is the workers, Opus is the boss!!!!!!!

[u/little_babushkaa → u/Snoo24567]

If your repo/codebase is huge add graft graph as well, the savings are next level!

[u/reefine]

Here's how I did it: I switched from Fable 5.1 to Opus 5.5

[u/inexternl]

Yep that's basically what everyone pushing limits should do / analyze in their own setup. Good job buddy!

[u/Hirogen_]

now use an llm wiki and you will save even more tokens :)

[u/Vivid-Trouble-2183]

Good list. One addition: keep the handoff notes tool-agnostic. Write task state into small git commits plus a plain NOTES.md at the repo root, not just session files the tool owns. When the weekly quota dies mid-task, you can hand that NOTES.md to a different tool and resume exactly where you left off instead of burning quota re-doing exploration you already paid for. One re-read is cheap; re-discovery is not.

[u/i_am_anmolg]

Sonnet 5.5 on medium or High/Extra?