So what does that mean? Claude within ACP within my editor is billed differently than Claude via CLI?
gcr 11 minutes ago [-]
As a fellow zed user, I fear this could affect us (though i'm not 100% confident). Zed uses their own adapter to implement claude's ACP support, and it's likely using `claude -p` (the agent SDK) under the hood.
Hoping the Zed team will clarify.
puglr 2 hours ago [-]
It'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.
solenoid0937 47 minutes ago [-]
It's not bad at all. You get $200 in monthly extra usage credits. Unless you are a deeply unprofitable user this change is no big deal.
brianwawok 13 minutes ago [-]
The $200 plan is easily providing $2000 of AI usage. So with this change your bill goes from $200 to $200 + $2000 -$200 = $2000. That’s a 10x jump.
Stuff like gas town is dead in the water
sigseg1v 30 minutes ago [-]
is using a Ralph loop for all tasks with "claude -p" and using my weekly limit up to 100% considered some kind of unprofitable outlier? It's a command line tool, it would be ridiculous to expect that a large number of users don't do this. I never launch "claude" interactively by itself.
My understanding is that now with this workflow I will pay the same amount but get much less usage before getting to 100% for the week. How is that not bad?
gcr 7 minutes ago [-]
[dead]
mkw5053 1 hours ago [-]
Out of curiosity, how are you using it and for what?
puglr 10 minutes ago [-]
Lots and lots of automation, along with long-running multi-instance headless tasks. My usage, which I was on the verge of increasing via a second Max plan, would cost 3 figures per day, rather than per month. I already know this because my initial tooling was prototyped against direct API usage, and that was the cost of my usage patterns.
That is not sustainable for me. I understand that Anthropic can't subsidize all of us forever, but this will force me away from claude which is unfortunate. A number of the people I work with are similarly affected.
paulddraper 1 hours ago [-]
Yeah, it's a pretty wild change.
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.
You also get $200 in monthly credits so it's not bad.
aselimov3 3 hours ago [-]
Where are you seeing that info?? The link you posted says nothing about -p
ramoz 2 hours ago [-]
I wasn't able to post the official links because it was already posted by simple reposters who didn't understand, and titled their HN posts as "you get credits" basically
I mean it does cost you API rates, you just get a certain amount of credit by having a subscription.
3 hours ago [-]
solenoid0937 45 minutes ago [-]
Before 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.
ramoz 44 minutes ago [-]
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.
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.
ramoz 31 minutes ago [-]
Yea that's fine and understandable.
But like I said, this is something for those users. I launch many review processes locally with `claude -p`
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.
ramoz 2 hours ago [-]
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.
Hoping the Zed team will clarify.
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.
Stuff like gas town is dead in the water
My understanding is that now with this workflow I will pay the same amount but get much less usage before getting to 100% for the week. How is that not bad?
That is not sustainable for me. I understand that Anthropic can't subsidize all of us forever, but this will force me away from claude which is unfortunate. A number of the people I work with are similarly affected.
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.
[1] https://status.claude.com/
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.
this is the original thread https://x.com/ClaudeDevs/status/2054610152817619388?s=20
This is a nothing burger.
https://x.com/jeremyphoward/status/2054682882753597603?s=20
But like I said, this is something for those users. I launch many review processes locally with `claude -p`
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.