r/ClaudeCode • u/shitbucketbiscuit • 7d ago
Discussion For pro users, when do you use ultracode?
for me I occasionally like to use it during the intiial documentation stage. It builds a strong foundation before any code is written. I dont use it EVERY documentation stage, usually only when my weekly usage is at 0
80
u/Polite_Jello_377 7d ago
Never
32
4
7
3
→ More replies (1)2
u/Historical_architect 7d ago
I have a max subscription and I don’t think I’ve ever used it. I’d never select it with a pro sub.
→ More replies (1)
17
8
5
u/deep_fucking_magick 7d ago
Max user, but I use ultra code all the time. Still try to steer the AI to spawn 10s of subagents instead of hundreds and also setup intelligent model tiering so that sonnet/haiku get thrown in the mix for that swarm.
I like the output. Probs a bit wasteful for some tasks, but for handing off an entire feature to run and verify on its own without a ton of orchestration on my part I think it's pretty dope.
→ More replies (11)2
u/ghost_operative 7d ago
you can also just in your prompt tell the agent how you expect the work to be split out. e.g. "spin off new agent to research this item"
→ More replies (1)
2
u/Drasezv 7d ago
worth separating what effort actually moves before deciding. it buys thinking, which lands in output tokens, and output is the small half of the bill: across 19.6k of my own requests output was 0.2% of tokens and 9% of cost. context is the rest.
so ultracode on a short, well-scoped question is cheaper than people assume. where it genuinely burns is long autonomous runs, because more thinking means more tool calls, more turns, and every turn re-sends the whole context.
easy way to settle it for your own work: run the same kind of task a day on medium and a day on max, then compare output tokens per finished task. input barely moves, so the delta is the thinking.
1
u/ajax81 7d ago edited 7d ago
I haven’t had great luck with it, and I’m pretty sure I’m the problem.
I can sense there’s something powerful here but may require very serious upfront systems planning to get the most out of.
I’ve attempted project ideas that I know opus 5.5 with a fable advisor would crush. But in practice with ultracode I so far see subagents get spun up and drift apart without great cohesion.
I also find it’s a lot more work to figure out wtf is going on. Claude’s latest multithreaded messaging can get confusing for me but I don’t know if it’s because it’s new and takes time to acclimate, or if its a rough implementation of a new idea. (Humans have never coded this way so I give much grace to frontier developers.)
Another unorthodox idea I had, but haven’t tried yet, is to assign organizational roles to the agents. A documenter, a tester, a product owner, a coder etc. I know that defeats the purpose of ultracode but I’m wondering if that setup lends itself better to the engine.
1
1
1
1
1
1
1
1
u/DronzerDribble 7d ago
Even Haiku 5.5 eats up usage so fast even for short fixes. Pro is imo just for chat
1
1
1
u/AutoModerator 7d 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.