1d • Feature Updates
Claude Code session caps just doubled
Anthropic raised the thresholds this week. Here is what actually changed, what did not, and how to make your Claude session go further.
**What changed (May 06):**
- Claude Code 5-hour session limits **doubled** for Pro, Max, Team, and Enterprise.
- Peak-hours throttle on Claude Code **removed** for Pro and Max.
- Claude Opus API rate limits raised "considerably."
- Powered by a new SpaceX compute deal: 300+ MW of capacity, around 220,000 NVIDIA GPUs.
**What did NOT change:**
- Weekly limits. If you were hitting the weekly cap last month, you will still hit it this month.
- The change buys you more in a single session, not more across a week.
---
## 5 ways to stretch your Claude session (desktop users)
**1. Use Projects, stop re-pasting the same context.**
If you keep pasting the same brief, doc, or code file into every new chat, move it into a Project once. Every conversation inside that Project sees those files automatically. You stop burning your session limit re-uploading the same information, and Claude stops re-reading it.
**2. Start a new chat when the topic changes.**
Every message in a long chat sends the entire history back to Claude. After 30 or 40 turns, you are paying (in session usage and in speed) for the first message every single time. When you switch topic, start fresh.
**3. Pick the right model for the task.**
Haiku for quick lookups, summaries, and short questions. Sonnet for normal day-to-day work. Opus only when the task is genuinely hard (architecture, dense reasoning, long multi-step analysis). Most people leave Opus on for everything and burn through the limit much faster than they need to.
**4. Be specific in your first message.**
Vague prompts trigger 5 rounds of clarification. One precise prompt with full context and constraints lands the answer in one shot. Spend 30 seconds writing the prompt, save 10 minutes of back and forth.
**5. Use Artifacts instead of asking for full rewrites.**
When Claude builds a doc or code in an Artifact, you can ask for targeted edits ("change section 2 only"). Asking "rewrite the whole thing" makes Claude regenerate everything and uses far more of your session.
---
## Building on the API? 3 advanced wins
For developers using the Anthropic SDK or Claude Code in code projects.
**Prompt caching:** mark stable context (system prompt, doc corpus, codebase) with `cache_control`. Cache reads cost ~10% of normal input tokens. Put stable content first, dynamic content last. Cache works on a prefix only.
**Batch API:** 50% off for any non-realtime job (backlog summarization, embeddings, evals). Results within 24 hours.
**Subagents in Claude Code:** spawn subagents for parallel research. Each gets its own context, reports back compressed findings, and the main session stays lean. Run `/compact` between phases of work.
---
**Try this week:**
Pick one workflow you have been pasting the same context into every time. Move that context into a Project. Run your next 3 prompts inside the Project and notice how much faster you reach the answer.
**Question for you:** What is the one thing you keep re-pasting into Claude that should really live in a Project? Drop a comment.
3
2 comments
Claude Code session caps just doubled
powered by
skool.com/claude-learning-skool-9159
Master Claude AI from first prompt to production. 30 video modules, 4 levels, 7 learning paths.
Suggested communities
Powered by