99% of my max plan usage is non-interactive, and this post-June 15 pricing will far, far exceed what I can afford. I assume this applies to a great deal of us.
Claude subscription changes coverage of `claude -p`
11–20 of 62 posts
Re: Claude subscription changes coverage of `claude -p`
#12It's a bit disheartening that this is generating so little discussion (this thread seems to be the one with the most comments, currently at 8). 99% of my max plan usage is non-interactive, and this post-June 15 pricing will far, far exceed what I can afford. I assume this applies to a great deal of us.
Re: Claude subscription changes coverage of `claude -p`
#13Title is misleading. (EDIT: Has been updated) https://x.com/ClaudeDevs/status/2054610152817619388 You can claim a monthly credit that covers programmatic (`claude -p`, etc) usage. So a Claude subscription does cover it, but at a lesser amount.
Happy to change the title if there is explicit clarity on what my `claude -p` usage costs me today & it not differing from what it'll cost me once the change is in effect.
Re: Claude subscription changes coverage of `claude -p`
#14It's a bit disheartening that this is generating so little discussion (this thread seems to be the one with the most comments, currently at 8). 99% of my max plan usage is non-interactive, and this post-June 15 pricing will far, far exceed what I can afford. I assume this applies to a great deal of us.
It's one thing for Anthropic to ban subscription usage of OpenCode etc of their backend.
It's another thing to use their tools and still not get the full usage.
Claude's recent one 9 of uptime [1] might have something to do with it.
Re: Claude subscription changes coverage of `claude -p`
#15It's a bit disheartening that this is generating so little discussion (this thread seems to be the one with the most comments, currently at 8). 99% of my max plan usage is non-interactive, and this post-June 15 pricing will far, far exceed what I can afford. I assume this applies to a great deal of us.
Re: Claude subscription changes coverage of `claude -p`
#16The wording in the press is very confusing. Not sure if deliberate. If you're an active `claude -p` user, it will now cost you API rates vs being able to user your subscription. UPDATE: https://x.com/lydiahallie/status/2054650920768807313?s=20 Still confused.
Re: Claude subscription changes coverage of `claude -p`
#17This is a nothing burger.
Re: Claude subscription changes coverage of `claude -p`
#18Before the doomers come in, you get $200 in API credits every month for claude -p usage. Usage counts against those API credits. This is a nothing burger.
Re: Claude subscription changes coverage of `claude -p`
#19Before the doomers come in, you get $200 in API credits every month for claude -p usage. Usage counts against those API credits. This is a nothing burger.
This is much of a something burger for users who actively use `claude -p` under their subscription. Users will have to do their own math, but that 200 could come and go quite fast and then you're hitting normal API rates versus what you had previously been hitting. https://x.com/jeremyphoward/status/2054682882753597603?s=20
Re: Claude subscription changes coverage of `claude -p`
#20Earlier quoted context omitted.
This is much of a something burger for users who actively use `claude -p` under their subscription. Users will have to do their own math, but that 200 could come and go quite fast and then you're hitting normal API rates versus what you had previously been hitting. https://x.com/jeremyphoward/status/2054682882753597603?s=20
Sure, but if you spend that many tokens you're probably a pretty big net loss for the company anyways. No company will subsidize that level of compute for you indefinitely.
But like I said, this is something for those users. I launch many review processes locally with `claude -p`