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 recentry read a book that presentes its content as ramble poetry, a post-ironic reference heavy text. I feel that is a suitable description for this readme page.
I'm not familiar with this at all. But at first blush, it seems like the Readme is far more interested in being angry with Anthropic than actually telling me what this is or why I care.
I see "Multi Agent Orchestration", but, scrolling through this I still have no idea what I'm looking at.
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".
For those who've been tracking the Oh My OpenCode and Anthropic fight.
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.
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?
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…
This feels like reading about some kind of obscure roleplaying game. As far as I can understand:
- there was a CLI based on OpenCode, that depended on extracting the auth token used by Claude Code
- Anthropic found a way to prevent this
- This person (or AI) reimplemented similar workflows using custom commands inside Claude Code instead
It appears that Anthropic is totally in their right to do this. Third party software is meant to use the API instead. It sucks that it's so much more expensive, but it's their decision to make,
Meanwhile, this seems like a good approach, both sides win. The project page would benefit from skipping all the drama and focusing on being a helpful intro.