31–40 of 62 posts
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.
Subscription usage refills every five hours. API billing doesn't.
Earlier quoted context omitted.
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 al…
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 a…
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.
You're not understanding the difference between API billing and subscirption billing. Subscription usage refills every five hours. API billing doesn't.
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.
https://github.com/agentclientprotocol/claude-agent-acp/blob...
But inevitably, this will end, ultimately making AI a bit less accessible for consumers.
Earlier quoted context omitted.
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 we…
If anything you might be an outlier if you do this and are actually producing something of reasonable value down the line.
They know if the value provided by subsidized usage is too low, they're literally burning dollars for nothing: people won't feel any great pain losing it one day and definitely won't convert.
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.
I mean it does cost you API rates, you just get a certain amount of credit by having a subscription.
Still interactive (conforms to spirit of Anthropic's new rule), and runs Claude Code via the actual CLI (conforms to letter of Anthropic's rule), without even using the JSON output flag. It would just read the outputs directly from the terminal like a user would, and then translates the user's actions directly into actions to the Claude Code TUI.
Tradeoffs: the thinking blocks are lost, and file changes from edit tools might have to be reconstructed after-the-fact using VCS commands because the TUI doesn't display them when accept-edits mode is enabled. Requires underlying terminal to have a giant width/height in order to reliably capture the outputs by reading the terminal alone. Interactive tools like AskUserQuestion will need to work via detecting that such a prompt is open and exposing the original CLI interface to the user temporarily.
But overall it seems like it could give users most of the benefits of an interactive GUI interface (scrollable history, much higher info density, easy to copy text, browse features with mouse) while staying compliant with Anthropic's new rules both in letter and spirit. You can then build a worktree manager or whatever above this agent GUI layer. This way us interactive users can have our good tools back (and leverage the new claude -p credit for occasional automation features) while the people who are actually abusing the plan with 24/7 dark factories or openclaw are still locked out.
(the only way Anthropic would not agree to this is if they had the ulterior motive of lock-in in mind...)