[URGENT] Increase weekly Sonnet rate limits by at least 50%

[URGENT] Increase Weekly Sonnet Rate Limits by at Least 50%

Summary

Current weekly rate limits for Claude Sonnet are severely insufficient for professional development workflows and are causing critical interruptions that leave users without service mid-project.

Problem Statement

Current Impact (Critical):

• ✅ Professional projects require continuous Claude Code assistance
• ❌ Weekly limits reached mid-project → Work stops completely
• ❌ No service available when limits hit → Developers blocked
• ❌ Productivity loss → Cannot complete time-sensitive tasks
• ❌ Professional credibility damaged → Cannot deliver on deadlines

Real-World Example:

Monday-Thursday: Active development on Next.js portal
Thursday 3pm: "Weekly rate limit reached"
Friday-Sunday: ZERO service available
Result: 3 days of ZERO productivity, project delayed

Why This is Extremely Urgent

1. Professional Use Cases are Blocked

• Enterprise development requires consistent access
• CI/CD pipelines depend on Claude Code
• Client deliverables have deadlines
• Current limits assume hobbyist usage, not professional workflows

1. Competitive Disadvantage

• GitHub Copilot: Unlimited usage with subscription
• Cursor: Higher rate limits
• Claude Code: Severely restricted compared to competitors

1. User Experience Impact

• Users pay for Claude Pro ($20/month)
• Expect reliable, consistent service
• Getting less than 5 days of productive work per week
• Unacceptable for paid professional tool

Requested Changes

Minimum Request (Immediate):

Increase weekly Sonnet rate limits by 50%

Example:

• Current: ~500 messages/week → New: ~750 messages/week
• Current: ~100K tokens/day → New: ~150K tokens/day

Ideal Solution (Medium-term):

Tiered Rate Limits Based on Subscription

• Claude Free: Current conservative limits
• Claude Pro: 2x current limits (professional use)
• Claude Team: 5x current limits (enterprise use)
• Claude Enterprise: Unlimited or very high limits

Alternative Workaround (Short-term):

Allow users to purchase additional rate limit boosts

Example:

• Base Pro subscription: Current limits
• +$10/month: +50% rate limit
• +$20/month: +100% rate limit

Community Feedback

This issue affects all professional Claude Code users:

From our team:

"Los límites actuales son muy cortos e interrumpen los proyectos y nos quedamos sin servicio, esto es algo extremádamente urgente y severo."

Translation: Current limits are too short, interrupt projects, and leave us without service - this is extremely urgent and severe.

Impact on Claude Code Adoption

Current State:

• ❌ "Claude Code is great but runs out of quota too fast"
• ❌ "Can't recommend for professional use due to rate limits"
• ❌ "Constantly hitting weekly limits mid-project"

With Increased Limits:

• ✅ "Claude Code is reliable for professional development"
• ✅ "Can depend on it for client projects"
• ✅ "Competitive with GitHub Copilot for daily use"

Technical Considerations

Why Higher Limits are Justified:

1. Claude Code is more efficient than web Claude

• Uses specialized agents (Haiku for many tasks)
• Context is managed better (auto-compact)
• Less token waste than chat interface

1. Professional users generate value

• Build real products with Claude Code
• Evangelize the tool to teams
• Pay for Pro/Team subscriptions
• Should be rewarded with higher limits

1. Cost-benefit for Anthropic

• Happy professional users → More Team/Enterprise sales
• Word-of-mouth marketing from productive users
• Competitive positioning vs GitHub Copilot/Cursor

Comparison with Competitors

| Tool | Rate Limits | User Feedback |
|------|-------------|---------------|
| GitHub Copilot | Unlimited* | "Never worry about limits" |
| Cursor | High limits | "Rarely hit limits" |
| Claude Code | Restrictive | "Constantly blocked mid-week" |

*With paid subscription

Priority Justification

CRITICAL PRIORITY because:

1. ✅ Affects ALL professional Claude Code users
2. ✅ Causes complete service interruption (not degradation)
3. ✅ Blocks revenue-generating work
4. ✅ Damages Claude Code's professional credibility
5. ✅ Simple to implement (configuration change)
6. ✅ High user satisfaction impact

Proposed Timeline

• Immediate (This Week): 50% increase to weekly limits
• Short-term (1 Month): Tiered limits by subscription
• Medium-term (3 Months): Usage analytics dashboard for users

User Testimonials

Our team's experience:

• Project: Next.js enterprise portal with 292 routes
• Issue: Hit weekly limit Thursday, blocked until Monday
• Impact: 3-day delay on client deliverable
• Request: At least 50% increase in limits ASAP

Conclusion

Current weekly rate limits are severely insufficient for professional use and are causing critical interruptions that leave users without service.

This is extremely urgent and severe.

We strongly request:

1. Immediate: 50% increase in weekly Sonnet limits
2. Short-term: Tiered limits based on subscription tier
3. Transparency: Usage dashboard so users can track consumption

Thank you Anthropic team for considering this urgent request. Higher rate limits would transform Claude Code from "frequently blocked" to "reliably productive" for professional users.

---

Reported by: Eddy Murias (Professional Claude Code User)
Urgency: CRITICAL
Impact: Blocks all professional work when limits hit
Request: Minimum 50% increase in weekly Sonnet rate limits