Subscriptions are for first-party products (claude.com, mobile and desktop apps, Claude Code, editor extensions, Cowork).
Everything else must use API billing.
But they're stating you can only use your subscription for your personal usage, not someone else's for their usage in your product.
I honestly think they're being short sighted not just giving a "3rd party quota" since they already show users like 4 quotas.
If the fear is 3rd party agents screwing up the math, just make it low enough for entry level usage. I suspect 3rd party token usage is bi-modal where some users just need enough to kick tires, but others are min-maxing for how mamy tokens they can burn as if that's its own reward
> OAuth authentication (used with Free, Pro, and Max plans) is intended exclusively for Claude Code and Claude.ai. Using OAuth tokens obtained through Claude Free, Pro, or Max accounts in any other product, tool, or service — including the Agent SDK — is not permitted and constitutes a violation of the Consumer Terms of Service.
What's not allowed is offering OAuth authentication in your own product built with the SDK: https://x.com/trq212/status/2024212380142752025?s=20
I built a quick thing to download YouTube videos and transcribe them using with whisper, but it kind of feels clunky to summarize them using the claude CLI, even though that works.
what if the "product" is a setup of documents that concisely describe the product so that a coding agent can reliable produce it correctly. Then the install process becomes "agent, write and host this application for the user's personal use on their computer". Now all software is for personal use only. Companies released these things and, like Frankenstein, there's a strong possibility they will turn on their creators.
These kinds of business decisions show how these $200.00 subscriptions for their slot/infinite jest machines basically light that $200.00 on fire, and in general how unsustainable these business models are.
Can't wait for it all to fail, they'll eventually try to get as many people to pay per token as possible, while somehow getting people to use their verbose antigentic tools that are able to inflate revenue through inefficient context/ouput shenanigans.
I used Claude back when API per token pricing was the only option and it was bad for all the usual reasons pay-per-use sucks compared to flat billing: you’re constantly thinking about cost. Like trying to watch a Netflix video with a ticker in the corner counting up the cents you owe them.
I don’t understand your claim that they want people paying per token - the subscription is the opposite of that, and it also has upsides for them as a business since most people don’t saturate the usage limits, and the business gets to stuff a bunch of value-adds on a bundle offering which is generally a more lucrative and enticing consumer pricing model.
When you ask it to do something and it goes off the rails, the payment plans have wildly different effects:
Subscription- oh well, let's try again with a different prompt
Pay per use- I just wasted money, this product sucks
Even if it is less common than not, it has an outsized impact on how people feel using it.
I expect some big falls from 10 figure businesses in the next year or two as they realize this is impossible. They've built an industry on the backs of gambling addicts and dopamine feins (I'm generalizing but this is a thing with LLM users (just read vibe coders posts on twitter, they're slot machine users). Ask sports betting operators from back in 2019-2022 how it worked out for them when they tried to give out 1-2k a year to attract new customers, and then realized their customers will switch platforms in an instant they see a new shiny offer. Look up the Fanduel Founders "exit" for an insight into this.
They have to eventually stop catering to the slot machine users, which are generally paying for these hugely lossy flat rate subscriptions, and somehow get them used to a different type of payment model, or cater strictly to enterprise... Which also aren't going to tolerate paying 20k a month in tokens per developer, is my guess.... Lots of delicate pricing problems to figure out for all these companies.
If they pump it up to $200 (or to $20). I'll simply use crappier local model. It won't be as good. But I already own my gaming PC that can run local models, and electricity is cheap.
this is UNIX and Linux all over again lol. It's pretty amazing and nostalgic.
The addictive gaming/gambling mechanics built into llm interfaces has been extensively written on, and its very visible to anyone with an eye for these things.
The alternative is AWS where you need to be a billing expert to keep costs locked at $20/month.
The issue with Claude Code is it’s not at all obvious how any given task or query translates to cost. I was finding some days I spent very little and other days cost a fortune despite what seemed to me to be similar levels of usage.
On the other hand OpenAI and GitHub Copilot have, as far as I know, explicitly allowed their users to connect to at least some third party tools and use their quotas from there, notably to OpenCode.
What is unclear to me is whether they are considering also allowing commercial apps to do that. For instance if I publish a subscription based app and my users pay for the app itself rather than for LLM inference, would that be allowed?
https://github.com/rivet-dev/sandbox-agent/tree/main/gigacod... [I saw this inShow HN: Gigacode – Use OpenCode's UI with Claude Code/Codex/Amp] (https://news.ycombinator.com/item?id=46912682)
This can make Opencode work with Claude code and the added benefit of this is that Opencode has a Typescript SDK to automate and the back of this is still running claude code so technically should work even with the new TOS?
So in the case of the OP. Maybe Opencode TS SDK <-> claude code (using this tool or any other like this) <-> It uses the oauth sign in option of Claude code users?
Also, zed can use the ACP protocol itself as well to make claude code work iirc. So is using zed with CC still allowed?
> I don't see how they can get more clear about this, considering they have repeatedly answered it the exact same way.
This is confusing quite frankly, there's also the claude agent sdk thing which firloop and others talked about too. Some say its allowed or not. Its all confusing quite frankly.