Idk, I'm skeptical. Is there any proof that these multi agent orchestrators with fancy names actually do anything other than consuming more tokens?
I have a specific use case (financial analysis), that is at the edge of what is possible with this models (accuracy wise).<p>Gemini 2 was the beginning, you could see this technology could be helpful in this specific analysis but plenty of errors (not unlike a junior analyst). Gemini 2.5 flash was great actually useable, errors made were consistent.<p>This is where it gets interesting, I could add additional points to my system prompt, yes it would fix those errors but it would degrade the answer elsewhere, often it wouldn't be incorrect but merely much simpler less nuanced and less clever.<p>This is where multi-agents helped it actually meant the prompt can be broken down so that answers remain "clever". There is a big con to this, it is slow, slow to the point that I chose to stick with a single prompt (the request didn't work well operating in parallel).<p>However Gemini 3 flash is now smart enough that I'd now consider my financial analysis solved. All with one prompt.
It's hard to accurately measure but one advantage that the multi-agent approach has seems to be speed. I routinely see Sisyphus launching up to 4 sub agents to read/analyse a file and/or to do things in parallel.<p>The quality of the output depends more on the underlying LLM. GLM 4.7 isn't going to beat Opus but Opus with an orchestra seems to be faster and perhaps marginally better than with a more linear approach.<p>Ofcourse this burns a lot of tokens but with a cheap subscription like z. ai or with a corporate budget does it really matter?
This seems great, but installing a bunch of prompt from an hackernews/github account with no history seems like something you shouldn't do. Especially with "silent auto-upgrade".
This removes the primary advantage of opencode, easy access to many models to avoid hammering a single service. Absolutely unusable to anyone with a pro sub.
For those who've been tracking the Oh My OpenCode and Anthropic fight.
That has really been the "OpenCode and Anthropic" fight, OMO is still a tiny player compared to all OpenCode (and other such clients) usage.
Do you have a link to some background? I'm curious why it was banned.
They banned it because it’s the current way tech companies are expected to operate.
It sounds pretty reasonable to me that they sell a subscription without API access at a different price than the one with that feature. It's obviously a very useful feature or the workaround wouldn't exist, right?<p>To me it sounds like the CLI subscription is a loss-leader designed to get you hooked so you'll upgrade once you realize it's valuable enough to pay extra for the "premium" features. It also sounds pretty reasonable to ban products designed to cheat them out of the difference in cost.<p>Am I missing some nuance, or is this just internet people being cheap?
The cli subscription actually actively cannibalizes the API business in my experience. I think this is a product decision: if you use it to code, they want to control the user experience.<p>If you use it to back up 100,000 MAUs, then they want you to use the API.<p>I was originally an API user but the cli subscription is so much cheaper that I switched over. This is a combination of th CLI getting much more useful and reasoning models using many more tokens.
Comparing this to API access feels odd to me. Opencode does not magically convert your subscription into API usage. It is just an alternative to the official CLI. It has a web UI, smoother UX, and less flickering. Nothing groundbreaking, but it is pretty annoying that even something as simple as tagging files with @ is still so laggy.
<a href="https://news.ycombinator.com/item?id=46549823">https://news.ycombinator.com/item?id=46549823</a>
If I have a team of developers should I be enforcing this type of multi-agent setup for development? Has this tech reached the level of being better than your above average developer at implementing well specified features? Has anyone had success doing this?
If you're an engineering manager, you should communicate with your team, know their strengths and weaknesses, stay sharp on modern technique, and, most importantly, ask <i>them</i> what workflows work best for them, not us on Hacker News.<p>If you're hiring a consultancy or a pile of freelancers it's a bit different, but the question here would make me believe you don't trust their capability to start and I would be looking for teams that better align with what you expect as their outputs.
In my experience multi-agent orchestration frameworks usually accomplish vague to unnoticable to straight up worse results compared just getting used to the vanilla tools before impulsively installing the daily flavor of "I made Claude Code better". I'm guessing you've probably already noticed by now these come out daily. But a look at the repo shows that they do at least halfway use sub-agents in the way most people are starting to realize they're (currently at least) most helpful imo, which is managing context bloat in the main chats. Not a fan of wishfully creating "expert" agents which amount to little more than prompts asking Claude to a good job at the task. I'm honestly not sure why that couldn't be a slash command at that point.
Enforce?
No. Just, no to all of this
Just pay for the API access.
Huh? You don't need all of this to program effectively with Claude. You just need a daft idea, a bad API sketch and patience. A large vocabulary of insults and swear words goes a long way as well.
Terrible name…