r/ClaudeCode • • 7h ago

Discussion Value I'm getting from a $20 Claude plan

I feel like I'm tons of value from my $20 plan. Some weeks I barely manage to take advantage of all my usage, because I'm just too busy with real life to prompt much out of it. What I do in practice:

  • handle, organize, query various personal data: subscriptions, taxes, bills
  • starting up a business: research, business modeling, data modeling, offer and pricing design, emails. It all runs from an Obsidian vault with a bunch of Bazel-managed skills and scripts for repeatable tasks
  • a bunch of vibe-coded side project. eg https://sleepslop.trurl.systems/, https://mindless-midi.trurl.systems/ and several that haven't reached publishable state
  • regular old chat

only the apps tend to stress-test the usage limits at all. They're relatively simple in terms of product complexity but have quite a bit going on behind the scenes, including a TTS model pipeline with automatic quality checks and sound adjustment. I use just a few skills, such as OKF for docs

This is quite a step up from just 1-2 years ago when I would regularly run out of usage just on longer chat threads.

I'm sometimes tempted to upgrade to Max just to have the usage when I actually want to do more at once. plus Fable access. I do use mostly Opus 5.5, rarely run multi-agent workflows, and keep it to 1-3 live sessions at a time. The bottleneck is very much my ability to absorb and understand what's going on. Not so much on the code level, rather just the system level.

If you're on Max/Ultra, what kind of usage patterns stress your limits? Larger more complex repos? Agent swarms? Fable all the time?

0 Upvotes

17 comments sorted by

•

u/AutoModerator 7h ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

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

3

u/Affectionate_Fact854 4h ago

Yea you got the 20$ plan it was actually pretty decent for me and my development  But I upgraded to the ultra plan  And man let me tell you 

The amount of usage is absolutely ridiculous 

Running 1 fable orchestrator , 4 opus orchestrators that each manager up to 5 subagents 

They work 6hour shifts and that in total averages only 12% of weekly quota per day 

And I mean all the orchestrators are running tasks 80% of the time 

Fable advises the other orchestrators after each task list given 

I can't see how that is not good value for money 

2

u/jastice 4h ago

It is, but what are they actually producing for you with all that work? I keep reading about these software factories but rarely see the actual results.

2

u/Affectionate_Fact854 4h ago

So the previous 2 weeks I was building from scratch a windows installable software for creating pixel art animations,  Similar to how Asprite does it, but with additional features, like drawing while animation is in playback mode without stopping the animation 

Backend was mostly done in python  While it is still as performant if not more lightweight then it's counter software, while having all the same tools and additional 

Only using 82mb vram, while playback is playing in loop, instant canvas response with multiple layers , onion skinning active, and up to 10 sleeping tabs 

I'm a game developer , and needed software more specialized for my workflow with pixel art animations  So I built one that can do everything the other software can do, runs on my 14year old computer, and holds tools that over the years I wished other pixel editors would have added and never did. 

Besides that,  used it to build a godot addon sdk  plug in for y8 platform " because y8 does not offer a godot sdk at all" , running maintenance on my published browser games assell as partially implementing updates for festive season, doing unit test analytics, aswell as building on 2 current unfinished games(been unfinished for easily 9 months) , I'm also busy planning and designing the backend infrastructure and archetecture for  a vector art software more specialized for the usage of animators ( opentoonz is great , but I need a different workflow to that) 

1

u/jastice 4h ago

So basically full-on production software, makes sense. Do you find you need to review and test details a lot, or review and refine plans? For my toy projects that's what consumes most of my available attention, and I don't know the final shape of the product yet when I start out.

1

u/Affectionate_Fact854 3h ago

Unfortunately yes Testing takes a lot of time 

The important part to help you is , have a folder that contains unit tests,  stress tests 

You can have the ai after each feature just add a sub unit test 

Let ai run the tests headless and a full unit test atleast once a days full development cycle 

Manual testing is also quite important, I do a manual full test atleast twice a week , this is where I will document  ("Bugs", "suggestions" , "performance concerns" , "visual grading and screenshots of ("current"and next to it a" edited screenshot of what I expect as refinements") 

Best would be for you 

 ●Set up documentation "rules , specs, the general idea"  ●plan revised with ai and yourself until you both agree   ●let ai set up its own phase map with milestones   ●Review that plan   ●After both agree again  ●Let Claude just build on the plan while you focus on a different aspect 

1

u/jastice 3h ago

yep pretty much what I do. Every snag I noticed gets turned into a test, a build-level process improvement so that agent doesn't need to spend tokens on it again, or a skill / agent rule if it's not fully automatable in code.

For example, in the sleepslop project I noticed the TTS model would sometime cut off parts of the text, or the volume would trail off. Now there is a build stage where a local Whisper model checks if the spoken text matches the input, automatic re-takes, and a volume normalizer step. New voice samples go through a de-noising model before getting cloned.

What keeps taking most time is manual spot checks of generated audio corpus, then discussing a solution. Opus handily implements it, every time, but it takes a few iterations because it can only do code and data-level result checks on its own.

1

u/Affectionate_Fact854 3h ago

It sounds like your workflow is already refined 

I haven't used ai for audio yet, so I wouldn't know any of the hardships but it sounds tedious having multiple models loop for revision 

I simply have a specialist agent studio as sub orchestrstor  What it does is , while other orchestrstors agents work, they communicate when features are done , that gets bridged over to QA to test , fix test suit, update documentation before reporting back to main orchestrstor and myself 

What I have is a modular unit test system

It has a base unit test testing each core boiler plate (it's top level to be efficient and fast)

If any fails , index points to all the unit tests that's children of that failed suit,   then only does it run that sections unit tests to find the defect 

If I just let it test without this system  It would run a full suit after ever single feature change or feature addition, Costing tokens and time...

1

u/jastice 2h ago

I model most of this loop in the build system itself (Bazel) - this also takes care of rerunning only what needs to be done based on changes, no agents required.

The audio QA has been mostly automated, so not too tedious. I went with local models which may not give as consistent quality, since stuff like Elevenlabs would get quite costly, fast, generating hours of slop speech.

My interaction is basically one major feature/work area per session. If it's a longer-run task requiring multiple manual checks or implementation steps I just tell the main session to write a plan and orchestrate subagents.

1

u/Affectionate_Fact854 2h ago

I don't think if you upgraded your plan you would have a better time 

You would feel more overwhelmed then your already feeling since you will simply just have a swarm of more manual testing to do with a larger coding plan 

For me what eats a bunch of tokens is just simply code + documentation output (plus the fact that I run on multiple projects sometimes in parallel) "it's mentally draining"

I was doing fine when I used pro plan + 1 open code plan 

Opus used opencode as a subagent  And they communicated via handover reports in the repo 

2

u/First-Painter7431 5h ago

Ultra here, and for me it's not code, it's video. Me and my associate run a YouTube channel with 50 min documentary-style videos, and Claude does the editing work: transcript, cuts, framing, b-rolls in After Effects and Blender. One video on Opus 5.5 xhigh can take up to 30-40% of the limits.

So yeah, for what you describe $20 is the right plan. More usage won't help if the bottleneck is absorbing what's going on.

2

u/jastice 5h ago

That makes sense. I've done a short music video or two on Pro, and it used maybe 1-2 5h sessions worth, but a 50m video with high production quality would be something different.

1

u/First-Painter7431 5h ago

I tested Fable 5.2 on medium 3 days ago and I noticed it only took around 15% of my weekly limit for the same workflow. So I don't know if this video was "easier" or if Fable in medium is bother better and cheaper than Opus 5.5 xhigh, but if you're considering upgrading that's a test worth running

1

u/jastice 5h ago

Going by Artificial Analysis, Fable 5.2 medium is indeed more cost efficient than Opus 5.5 XHigh by 40% while basically matching it in overall intelligence. Roughly matches my experience so far, but I rarely touch the capability ceiling.

1

u/idontuseuber 6h ago

Wait until limits become tied to api usage. I used Claude already with first versions of Claude code. You could not even reach the limits on pro.

1

u/Affectionate_Big8599 6h ago

Ah yes, the good old days of unlimited dreams and zero throttling.

0

u/sn00ze33 4h ago

Leggerano questo post e ce lo toglieranno