Earlier quoted context omitted.
You aren't paying to be using that limit all of the time. You are paying to be using that limit some of the time. There are 5 hour windows when you are sleeping and can't use it. There are weekend limits. Theoretically you can max out every 5 hour window, but they lose money on that. It's structured so users can have bursts of unlimited usage, and spend ~15% of the theoretical max cap, and that's still cheaper than a…
How can an OpenClaw user use 6 times what a human subscriber is using when I'm four hours into the week and 15% of my weekly limit is already used up, just by coding? OpenClaw can't use 600% of my weekly limits.
Basically; spin up in the morning eats a lot of tokens because the cache is cold. This has actually gotten worse now that Opus supports a 1Mt context.
So: compact before closing up for the night (reduces the size of the cache that needs to be spun up); and the default cache life is 5 minutes, so keep a heartbeat running when you step away from the keyboard to keep the cache warm.
Also, things like web-research eat context like crazy. Keep those separate, and ask for an md report with the key findings to feed into your main.
This is not exhaustive list and it's potentially subtly wrong sometimes. But it's a good band-aid.
https://news.ycombinator.com/item?id=47616297
Know what's funny? Openclaw might actually burn less tokens than a naive claude code user; if configured correctly. %-/