Well damn, I have claude code drive `claude -p` heavily during development, this makes my $200 a month plan (which I don't tap out of) significantly less attractive.
Yes it is $200 a month in "credits", but their accounting is already dodgy. We know this is going to get ratcheted in some way.
The weasel writing in the post is also not appreciated.
"Claude subscription plans are now eligible to receive a monthly Agent SDK credit."
"Starting June 15, 2026, Claude Agent SDK and claude -p usage no longer counts toward your Claude plan’s usage limits."
Please Anthropic, don't treat your customers like idiots.
Tracking with `ccusage`, I pretty easily hit $2000/mo in API equivalent credits and while I'd consider myself a power user, I'm a responsible one that's generally always in the loop. If I were using `claude -p`, this would effectively be a kneecapping.
Interesting move separating CLI and Agent SDK usage from regular chat limits makes sense, especially for people building automations. The question is whether the monthly credits will be enough.
Well damn, I have claude code drive `claude -p` heavily during development, this makes my $200 a month plan (which I don't tap out of) significantly less attractive.
Yes it is $200 a month in "credits", but their accounting is already dodgy. We know this is going to get ratcheted in some way.
The weasel writing in the post is also not appreciated.
"Claude subscription plans are now eligible to receive a monthly Agent SDK credit."
"Starting June 15, 2026, Claude Agent SDK and claude -p usage no longer counts toward your Claude plan’s usage limits."
Please Anthropic, don't treat your customers like idiots.
Tracking with `ccusage`, I pretty easily hit $2000/mo in API equivalent credits and while I'd consider myself a power user, I'm a responsible one that's generally always in the loop. If I were using `claude -p`, this would effectively be a kneecapping.
I was already preparing to move off of claude code, in many ways it is a false summit.
Been loving pi and codex lately. Good to build resiliency and self sufficiency into these systems.
Moving from CC to Codex would be the opposite of what I want. It would be like trading Burger King for McDonalds, both are bad for you.
It's trivial to build a wrapper script to emulate `claude -p` with full PTY without Claude knowing. Good old screen scraping to the rescue.
This new cat and mouse game is perhaps a sign of the times...
Interesting move separating CLI and Agent SDK usage from regular chat limits makes sense, especially for people building automations. The question is whether the monthly credits will be enough.
I assume this will affect things like using claude code inside of zed or vscode too?
Another step toward splitting chat and agent pricing.Make sense, but adds friction for anyone building real automation on top.
[dupe] https://news.ycombinator.com/item?id=48126438
rip conductor :(
Can you fill me in on how this impacts conductor? How are they using `claude -p`?