Here adoption is a combination on the tool and the model.
If people can’t pay the model to use the tool, they might not use the tool even if it’s better.
That’s what anthropic is doing.
It might be faster, but it’s more expensive.
The only way remains to try and lock consumers into your ecosystem.
Aside: it is pretty easy to let our appreciation* of OSS turn into a kind of confirmation bias about its value to other people/orgs.
* I can understand why people promote OSS from various POVs: ethics, security, end user control, pro-innovation, goodwill, and so on. I value all of these things. But I’m wary of reasoning and philosophies that offer merely binary judgments.
Adoption is how one wins. Look at all the crappy solutions out there that are still around.
It's not unheard of for companies that have strong customer mindshare to find themselves intermediated by competitors or other products to the point that they just became part of the infrastructure and eventually lose that mindshare.
I doubt Anthropic wants to become a swappable backend for the actual thing that developers reach for to do their work (the CLI tool).
Don't get me wrong, I think developers should 100% have the choice of tooling they want to use.
But from a business standpoint I think maintaining that direct or first-party connection to the developer is what Anthropic are trying to protect here.
Also it uses the Claude models but afaik it is constantly changing which one is using depending on the perceived difficulty.
Claude Code does the same. You can disable it in Kiro by specifically setting the model to what you want rather than “auto” using /model.
Tbh I’ve found Kiro to be much better than Claude Code. The actual quality of results seems about the same, but I’ve had multiple instances where Claude Code get stuck because of errors making tool calls whereas Kiro just works. Personally I also just prefer the simplicity of Kiro’s UX over CC’s relative “flashy” TUI.
but Claude Code cannot run without Claude models? What do you mean?
also while I was initially on the “they should open source” boat, and I’m happy Codex CLI did, there are a ton of benefits to keeping to closed source. just look at how much spam and dumb community drama OpenAI employees now have to deal with on GitHub. I increasingly think it’s a smart moved to keep it closed source and iterate without as direct community involvement on the codebase for now
They could close the issues and only allow discussions.
There was a project mentioned here recently that did just that.
*Edit
It was Ghostty,
"Why users cannot create Issues directly" - https://news.ycombinator.com/item?id=46460319
Claude Code feels like my early days when pair programming was all the rage.
If you have the time OpenCode comes the closest and lets you work across providers seamless.
"Should have" for what reason? I would be happy if they open sourced Claude Code, but the reality is that Claude Code is what makes Anthropic so relevant in the programming more, much more than the Claude models themselves. Asking them to give it away for free to their competitors seems a bit much.