Live data from Hacker News

Claude subscription changes coverage of `claude -p`

x.com

21–30 of 62 posts

Re: Claude subscription changes coverage of `claude -p`

#21
post #11

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.

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.

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?

Re: Claude subscription changes coverage of `claude -p`

#23
post #11

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.

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.

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

Re: Claude subscription changes coverage of `claude -p`

#25

So what does that mean? Claude within ACP within my editor is billed differently than Claude via CLI?

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.

Re: Claude subscription changes coverage of `claude -p`

#26
post #12
post #11

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.

Out of curiosity, how are you using it and for what?

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.

Re: Claude subscription changes coverage of `claude -p`

#27
post #11

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.

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.

[dead]

Re: Claude subscription changes coverage of `claude -p`

#29
This could end up becoming a cat-and-mouse game where users programmatically try to turn their non-interactive usage of Claude Code to appear interactive and Anthropic tries to detect and charge that under API pricing. I don't know if there's a proper solution here because there will always be borderline use cases like using Claude Code on a cloud VM, where it would be nicer to interactively do work through sending and receiving messages on a custom frontend rather than SSHing and using the CLI.

Re: Claude subscription changes coverage of `claude -p`

#30
post #2

The 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.

You also get $200 in monthly credits so it's not bad.

Ya but that monthly usage doesn't refill every five hours or every week the way your subscription usage does. Once you're through the $200, you're done until next month.
Post reply on HN