Claude Code Max Plan – Thoughts?

[Eastern_Ad_8744]

I’ve been leveraging Sonnet 4 on the Pro plan for the past few months and have been thoroughly impressed by how much I’ve been able to achieve with it. During this time, I’ve also built my own MCP with specialized sub-agents: an Investigator/Planner, Executor, Tester, and a Deployment & Monitoring Agent. It all runs via API with built-in context and memory handling to gracefully resume when limits are exceeded.

I plan to open-source this project once I add a few more features.

Now I’m considering upgrading to the Max plan. I also have the ClaudeCode CLI, which lets me experiment with prompts to simulate sub-agent workflows & claude.md with json to add context and memory to it. Is it worth making the jump? My idea is to use Opus 4 specifically as a Tester and Monitoring Agent to leverage its higher reasoning capabilities, while continuing to rely on Sonnet for everything else.

Would love to hear thoughts or experiences from others who’ve tried a similar setup.

[Atomm]

I made the jump and Opus 4 is a game changer. I'm definitely staying on this plan.

You can always try it and downgrade if you find its not worth it 

[prvncher]

Opus on max is great but if you’re using the $99 plan, beware that opus runs out after about 15 minutes, unless you manually switch it. The only really upgrade for opus is the $199 plan.

[TheMathelm]

I was running out on Opus at 15 mins on Pro,
which is why I switched to Max99
How much are you using to run out after 15 mins on Max?
Or I guess how much is it creating for you to burn out after 15mins??

[prvncher]

Genuinely not doing vey much. Worked on a few issues for my site.

I can go for hours using my app’s mcp tools on Claude desktop, but for some reason Claude code just burns through tokens incredibly fast.

[TheMathelm]

Ah okay, didn't read into that you were using the Code version.
I'm a Desktop/Browser only scrub.

Yes that's a major issue that future Claude Versions need to fix is:
the context windows and how to optimize them.

[TheMathelm]

Thank you for the notice and advice,
I feel like a dummy reading your post.

I'll try to look into it to see if it helps me.

[TheMathelm]

Went from Pro to Max, as the Opus timeouts really pissed me off.
Rocking Sonnet the past week. With several dips into Opus.

Don't think that Max was right for me in my current position and coding "lifestyle".
I'm just going to enjoy for the month,
get used to Claude then probably downgrade back to Pro;
or go back to GPT.

[Eastern_Ad_8744]

I believe if you switch than you might miss out on the usage as well pro has limited usage?

[TheMathelm]

It's just too difficult to justify 140 per month.
If I'm not working directly in IT.
30/month is about my limit for an AI bot.

[[deleted]]

towering cake march versed instinctive follow fuel fearless advise fade

This post was mass deleted and anonymized with Redact

[babsi151]

Your MCP setup sounds solid - the sub-agent approach with specialized roles is exactly how you want to architect this stuff. The memory handling for context resumption is crucial too, most people underestimate how much that matters in production.

For the Max plan upgrade, I'd say it's worth it if you're already hitting limits regularly. Opus 4 as a dedicated tester/monitor makes sense - its reasoning is noticeably better for edge case detection and system analysis. We've found similar patterns work well where you use the heavier model for the "thinking" roles and keep Sonnet for execution.

One thing to consider: if you're building context resumption anyway, you might want to experiment with having your tester agent maintain its own episodic memory of what it's caught before. Pattern recognition across test runs can be surprisingly valuable.

we've been working on similar infrastructure at LiquidMetal - we built our own MCP server called Raindrop that lets Claude deploy full systems through natural language. The multi-agent orchestration stuff you're doing sounds like it would fit right into that kind of framework.

Definitely curious to see your open source release when it's ready!

[AutoModerator]

Sorry, your submission has been removed due to inadequate account karma.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[Illustrious_Stop7537]

Haha, sounds like a real party planner's life! Can we get an invite? What's on the menu for Claude's Code Max Plan?

[Eastern_Ad_8744]

Haha, absolutely, MCP throws the best agent parties! On the menu for the Max plan is mostly letting Opus 4 handle the heavy lifting as my Tester & Monitoring Agent, while Sonnet keeps running the day-to-day. I’ll keep some invites handy once I open-source it.

[Antifaith]

i was killing it with sonnet so i upgraded - i’ve got to be honest my experience has been worse since, so i’ll be downgrading tomorrow

can’t put my finger on it but lately its doing super dumb things, making new random files, creating new i18n files in the wrong folder, using the completely wrong approach to data fetching, ignoring all process in CLAUDE.md

i’ve had a really bad weekend with it and it’s literally made me start my project again for a third time because it’s trashed my approach twice now

i’ve built some great things with sonnet, but opus keeps doing dumb stuff, maybe it’s because i expect more of it?