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.
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?
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.
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.
If you use it to back up 100,000 MAUs, then they want you to use the API.
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.
How do you think Claude Code and OpenCode communicate with Anthropic? Through the API. Maybe it's accessed slightly differently for subscription users. Anthropic is saying you can't use the API via a subscription anywhere you want. Only Claude Code can use it that way.
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?
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.
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 them what workflows work best for them, not us on Hacker News.
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.
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.
Idk, I'm skeptical. Is there any proof that these multi agent orchestrators with fancy names actually do anything other than consuming more tokens?
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.
It’s not hard to set up a router/proxy for Claude Code to use something else.
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?
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.
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.
If you use it to back up 100,000 MAUs, then they want you to use the API.
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.
How do you think Claude Code and OpenCode communicate with Anthropic? Through the API. Maybe it's accessed slightly differently for subscription users. Anthropic is saying you can't use the API via a subscription anywhere you want. Only Claude Code can use it that way.
https://news.ycombinator.com/item?id=46549823
Just pay for the API access.
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?
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.
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 them what workflows work best for them, not us on Hacker News.
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.
No. Just, no to all of this
Terrible name…
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.