Hey,

Is anyone else finding the usage limits on Claude's team plan a bit restrictive? My team and I keep bumping into the low thresholds, and it's really starting to hold us back. We've noticed that GPT-4 Teams allows for way more tokens and larger file sizes, which makes things much easier.

The thing is.. Claude is giving better results for us on all metrics when inside the limits it has.

Also, it would be awesome if Claude could support MongoDB vector search. This feature would really boost our projects and make a huge difference in our workflow.

Anyone else in the same boat? Would love to hear your thoughts or any tips you might have. And if anyone from Claude is listening, please consider these requests to help us out!

Thanks!

Claude has this 45 messages limit per 5 hours for pro subs as well. Is there any way to get around it?

Claude has 3 models and I have been mostly using sonet. From my initial observations, these limits apply for all the models at once.

I.e., if I exhaust limit with sonet, does that even restrict me from using opus and haiku ? Is there anyway to get around it?

I can also use API keys if there’s a really trusted integrator but help?

Update on documentation: From what I’ve seen till now this doesn’t give us very stood out notice about the limitations, they mentioned that there is a limit but there is a very vague mention of dynamic nature of limitations.

Edit (18 July, 2025):

Claude has tightened the limits of Claude Code silently, people are repeatedly facing this issue :: "Invalid model. Claude Pro users are not currently able to use Opus 4 in Claude Code" and also https://github.com/anthropics/claude-code/issues/3566

Make no mistake, I love claude to the core. I was probably in the mid-early adopters of Claude. I love the Artifact generation more than anything. But this limitations are really bad. Some power users are really happy on claude Max plan because they were able to get it to work precisely. I think this is more to do with Prompt engineering, and context engineering. I hope sooner or later, claude can really work like how ChatGPT is accessible now-a-days.

Edit ( 7 sept, 2025):

The fact that this post is still getting so much attention is a testament to Claude not listening to the users. I love Claude and Claude Code too much, and I am a fan of Anthropic adding new features. Unfortunately, this Claude code also hits the “Compacting conversation” too quick - for me atleast, and the limits are a little better honestly. But the cool down period is painful.

Okay guys, hear me out 😅

You know that annoying moment when you're coding with Claude and BAM - "5 hour limit reached" right in the middle of debugging? Yeah, it sucks.

So I discovered the limit works on a rolling 5-hour window from your LAST message, not your first.

My hack:

• 3 hours before I need Claude, I start sending random msgs every hour

• Just quick stuff like "hey" or "give me a fun fact"

• Takes 30 seconds lol

Result: When I actually start working, I'm already at hour 4 of the limit, so I get hour 5 PLUS a fresh 5-hour window = way more uninterrupted coding time 🎯

Is it janky? Yes. Does it work? ABSOLUTELY.

Anyone else doing this or am I just being extra? 😂 Drop your limit hacks below!

Tired of running into Claude.ai's daily limits? Try using Colada for Claude.

I actually enjoy Claude.ai's interface and artifacts implementation. I didn't want to lift and shift over to another LLM tool. So, to get past the daily limits, I decided to build a simple Chrome extension which continues conversations using your own Anthropic API key.

In short:

• Get past Claude.ai conversation limits (click on pineapple emoji the to activate Colada)
• Bring your own Anthropic API key (requests made directly from your machine)
• Preserve conversation context (scraped from the DOM)
• Simple, lightweight implementation (everything stored locally)

It's a $4.99 one-time purchase- just use "REDDIT" at checkout.

Let me know what you think. Open to any and all feedback.

Chrome Extension URL: https://chromewebstore.google.com/detail/colada-for-claude/pfgmdmgnpdgbifhbhcjjaihddhnepppj

I have Claude Pro ($20/month) and consistently run into the per-session usage limits when using Claude Code (CLI tool). I'll max out my current session and have to wait for the window to reset, even though I often end up using only 20-40% of my overall weekly allowance.

My budget is around $30/month total. Is there a better solution than Pro + occasional overage purchases?

Options I'm considering:

Paying for extra usage when I hit limits (but feels inefficient)

Switching to API pay-as-you-go for Claude Code specifically

Upgrading to a higher tier (but $100/month seems excessive for my usage)

For those who use Claude Code heavily in bursts but inconsistently week-to-week - what's your setup?

TL;DR: git init in ~/.claude/, delete old log lines (skip line 1), restart Claude Code = infinite conversation

⚠️ Use at your own risk - always backup with git first

Found an interesting workaround when hitting Claude Code conversation limits. The session logs can be edited to continue conversations indefinitely.

The Discovery: Claude Code stores conversation history in log files. When you hit the conversation limit, you can actually delete the beginning of the log file and continue the conversation.

Steps:

1. Setup git backup (CRITICAL)

   cd ~/.claude/
   git init
   git add .
   git commit -m "backup before log manipulation"

2. Find your session ID

   • In Claude Code, type /session

   • Copy the session ID

3. Locate the session log

   cd ~/.claude/
   # Find your session file using the ID

4. Edit the session file

   • Open in VSCode (Cmd+P to quick open if on Mac)

   • IMPORTANT: Disable word wrap (Opt+Z for Mac) for clarity

   • DO NOT touch the first line

   • Delete lines from the beginning (after line 1) to free up space

5. Restart the conversation

   • Close Claude Code

   • Reopen Claude Code

   • Continue sending messages - the conversation continues!

Why this works: The conversation limit is based on the total size of the session log. By removing old messages from the beginning (keeping the header intact), you free up space for new messages.

Risks:

• Loss of context from deleted messages

• Potential data corruption if done incorrectly

• That's why git backup is ESSENTIAL

Pro tip: When context changes significantly, it's better to just start a new conversation. But if you're stuck and need to continue, this is your escape hatch.

Found this while debugging session issues. Use responsibly!

And also i tried different solution for it, but not good as expected for now @yemreak/claude-compact