For most of last year, the number that ruined your afternoon was the 5-hour window. You'd hit it, take a coffee break, and come back. That era is ending. On Claude, the weekly limit is now the cap that actually stops work: even the new top plan drops the 5-hour cap for Claude Code but keeps the weekly one. On the OpenAI side, from December ChatGPT and Codex draw from one shared allowance, so a long chat about a design doc now spends the same budget your coding agent needs on Thursday.
Both changes push the same way: you need to budget for a week, not a session. Here's what's worked for me.
1. Know your real burn rate, not your vibe
Most people find out they're near the weekly cap when the agent stops. Instead, take three readings a day for one week: morning, after lunch, end of day. In Claude Code, /status shows where you are; for Codex, check the usage page in ChatGPT settings. Write the percentages down.
After a week you'll know two numbers: your average daily burn and your worst day. If worst day × 5 is over 100%, you will hit the wall in a normal week. That's the number to fix.
2. Treat one 5-hour session as a slice of the week
A common report right now: one heavy 5-hour session uses 15–20% of the weekly allowance. That means four or five intense sessions is your entire week. Plan around it:
- Split big tasks. One giant "refactor the whole module" prompt drags an ever-growing context. Five scoped tasks in fresh sessions are usually cheaper and better.
- Start fresh sessions often. Long sessions re-send long context. When a session drifts, summarize the state into a note and start over.
- Keep CLAUDE.md / AGENTS.md short. It rides along on every request. Move rarely used detail into separate docs the agent reads on demand.
3. Match the model to the job
Use the biggest model for planning, hard debugging and architecture. Use the smaller, cheaper model for renames, tests, boilerplate and status updates. Background subagents in Claude Code just got much cheaper for status updates, but the main loop still costs what it costs; route accordingly.
4. Budget chat and code together (Codex users)
Once ChatGPT and Codex share an allowance, the mental model changes:
- Decide a split, e.g. 70% coding agent / 30% chat, and check it mid-week.
- Do long brainstorming in a model you don't need for coding, if you have one.
- Don't paste huge logs into chat "just to ask"; trim them first.
5. Put the reset time where you can see it
The single most useful fact is not "how much have I used" but "am I burning faster than it refills, and when does it reset?" If the reset is Friday morning and you're at 85% on Wednesday, Thursday is a small-model day. If it resets tomorrow and you're at 60%, spend freely.
Write the reset day on a sticky note if you have to. The point is to never be surprised.
6. Have a fallback plan before you need it
When the cap hits mid-task, the cost isn't the tokens, it's the lost context. Keep a running NOTES.md in the repo that the agent updates as it works (what's done, what's next, open questions). If you have to switch tools or wait for the reset, you resume in minutes instead of rebuilding context from scratch.
7. A weekly routine that takes 5 minutes
- Monday: check where you start, note the reset time, decide your big-model days.
- Wednesday: check the burn rate. Above 60%? Shift to smaller models and scoped tasks.
- Friday / reset day: look back at what ate the most. Usually it's one runaway session or one enormous context.
Tools
Claude Code's /status and the ChatGPT usage page are enough if you check them. If you want the numbers always visible on a Mac, Peter Steinberger's free, MIT-licensed CodexBar puts them in the menu bar. Disclosure: I make TokenBar, which is built on CodexBar (tokenbar.site).
Whatever you use, the habit matters more than the tool: know your weekly burn, know your reset time, and match the model to the job. How are you handling the new limits?
This post was drafted with AI assistance.
Top comments (0)