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: 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. 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. Reduced context from 1M to 400K tokens A smaller orchestrator context, with subagents handling implementation in their own contexts, means less unnecessary context overhead. 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? submitted by /u/little_babushkaa
Originally posted by u/little_babushkaa on r/ClaudeCode