This is an unusual L for Anthropic. The unfortunate truth is that the engineering in opencode is so far ahead of Claude Code. Obviously, CC is a great tool, but that's more about the magic of the model than the engineering of the CLI. The opencode team[^1][^2] built an entire custom TUI backend that supports a good subset of HTML/CSS and the TypeScript ecosystem (i.e. not tied to Opencode, a generic TUI renderer). Th…
Anthropic blocks third-party use of Claude Code subscriptions
531–533 of 533 posts
Re: Anthropic blocks third-party use of Claude Code subscriptions
#532Earlier quoted context omitted.
It's hard to understand what Anthropic are getting from forcing more people to use Claude Code vs any other tools via the API. Why do they care? Do they somehow get better analytics or do they dream that there's a magical lock-in effect... from a buggy CLI?
Not that hard to understand, they want to control how their users use their product. A CLI they built, even acquiring the framework it was built in, is a way to achieve that.
Re: Anthropic blocks third-party use of Claude Code subscriptions
#533FWIW this isn’t new, using a Claude/Max subscription auth token as a general-purpose “API key” has been known (and blocked) for ages. OpenCode basically had to impersonate the official Claude Code client to make that work, and it always felt like a loophole that would get patched eventually. This is exactly why (when OpenCode and Charm/Crush started diverging) Charm chose not to support “use your Claude subscription”…
Yea exactly, I’m surprised people are calling this “drama”. It was from the beginning against the ToS, all the stuff supporting it just reverse engineered what Claude Code is doing and spoof being a client. I tried something similar few months back and Claude already has restrictions against this in place. You had to very specifically pretend to be real Claude Code (through copying system prompts etc) to get around i…