@NabilJB007 That overnight drop is rough. Funny thing, you working across 3 projects on Claude Code was probably what kept it low, more projects means more fresh contexts instead of one session growing all night
Two weeks ago I found out 99.9% of my Claude Code tokens were just the model re-reading its own context. My actual input: 0.03%.
So I changed how I work:
- one session = one task, then I close it
- no more marathon sessions that live for days
- when I need continuity, I write a short summary and start fresh instead of dragging the whole history
The difference is real. The sessions that used to quietly hit 100M+ don't happen anymore, because nothing is allowed to grow that big.
Turns out the fix was never a better plan or a cheaper model. It was just not letting context pile up.
Which raises the obvious question: is the fix just discipline? Close sessions at task boundaries, start fresh, paste your own summary if you need continuity.
Curious if anyone here actually does that consistently, or if we all just let sessions run until they die.
Someone posted their own token breakdown yesterday and the numbers lined up almost exactly with mine.
Him: 3B tokens, $3,586, across Claude Code, Codex, Cursor and Antigravity. 92.6% cache reads. Actual code output: 0.66%.
Me: Claude Code only. 99.9% cache reads. Output 0.4%. My own typed input was 0.03% of everything.
Two completely different setups, same shape. Almost nothing you pay for is the model producing work. It's the model re-reading context it already paid to write.
The gap between his 92.6% and my 99.9% is the interesting part. He runs four tools, so he's starting fresh contexts constantly. I live in one long Claude Code session until it collapses under its own weight. Spreading work across tools looks inefficient, but it accidentally keeps context small.
@DanylBnder This is what works: if you get a sudden surge of attention from a post or comment, you’re unlikely to be able to handle the influx, and it’ll only be temporary anyway; but if you take it step by step, you’ll get exactly what you deserve right now
Two weeks of building in public taught me the thing no one tells you: getting your first users is a completely different skill than building the product. And it's harder.
The stuff everyone assumes works, mostly doesn't:
- a link in your bio does almost nothing on its own
- replying under big accounts gets you views, but views aren't users
- and people won't try your thing just because it's free and solves their problem, attention is the real bottleneck, not interest
What actually works this early is unglamorous: go to people one by one, manually, find the ones who genuinely have the problem, and help them directly. Doesn't scale. That's fine, it's not supposed to yet.
Distribution is a craft. Turns out it's the harder half.