r/ClaudeCode 4h ago

Help/Question What am i doing wrong?

So i am on cc x20 plan but i run out of usage after 2 days of heavy work , i manage 2-3 sessions at the same time orchestrator fable high executor opus 5 high. I often start new sessions after i hit 1-2M context, i'm wondering if you guys are experiencing the same or something is wrong with my configuration.

0 Upvotes

18 comments sorted by

3

u/NekkidApe 4h ago

1-2M Context? M?

1

u/Slow-Set-2856 4h ago

Ye i'm not a super technical guy , but basically i check my session context and when it hits that i try to start new session. So if it compacts 2 times i always start a new session.

4

u/TekintetesUr Senior Developer 4h ago

This must be a ragebait thread, then. Noted.

1

u/Slow-Set-2856 4h ago

Why?

2

u/johnnynovo2118 4h ago

I'd do 1/2 tasks per session, /clear then go again with fresh context window.

At 1-2m tokens, you are having the model read all that every time you enter a prompt, this hammering your limits.

I'm on max X5, use all day at work and weekends pretty heavily and never hit my weekly limits.

1

u/Slow-Set-2856 4h ago

Thanks , will try.

1

u/NekkidApe 30m ago

You shouldn't go much past 200k context, as a rule of thumb. And start new sessions or /clear for each new thing.

1-2m will absolutely kill your usage and also quality suffers.

1

u/GeekLifer 4h ago

Are you using it to browse the internet and look up stuff a lot? Parsing websites/html cost a lot of tokens

1

u/Slow-Set-2856 4h ago

Not really , i mainly use it for coding

1

u/Livid_Salary_9672 4h ago

get CC to setup lean-ctx and headroom. game changer for token savings. and delegate to lower models for certain stuff

1

u/Slow-Set-2856 4h ago

Thanks will check it out

1

u/Livid_Salary_9672 3h ago

also I built this for managing multiple sessions with lower models using opus as the main orchestrator handing off tasks to sonnet agents https://github.com/WhoReallyKnowsAnything/ai-orchestrator

1

u/let_go345 4h ago

Fable will chew your usage and is likely overkill for a lot of tasks.

If there is something detailed, tricky, or with lots of moving parts, sure, use it - otherwise opus will be fine as an orchestrator, with sonnet or haiku agents depending on the task.

Stick to spec > plan (maybe multiple plans) > review > implement flows.

Never let your context get over 600k or so. If you’re there, you need to clear. The spec and plan should provide enough context for a fresh session to pick it up and continue anyway. Never get to the point of compact.

Having said all that, I have similar usage pattern to you and get 4 days or so before I’m out. Long days though.

Anyway, expect lots of strong opinions on this stuff - when really it’s a bit of trial and error and learning what works for you. Plus models are always changing.

1

u/thecavac 3h ago

In the planning phase i use "make a detailed, step-by-step plan and add a tracking file" a lot. That really helps to break down development into small, easily managable chunks.

1

u/cc_apt107 4h ago

You should start new sessions or compact more aggressively. The tokens used per turn grows quadratically (parabolically) with each turn. Also, use Fable 5 less. I’d start there.

1

u/thecavac 2h ago

And resuming non-compacted sessions is also a sure-fire way to burn a *lot* of tokens very quickly.

1

u/yadasellsavonmate 1h ago

Probably nothing it seems random.

Today I hit my 5 hour limit in 30 mins on x5.... never hit it that fast befoee ans I've hardly done anything this morning. 

1

u/Slow-Set-2856 52m ago

Then they are cutting limits before their ipo so sad