rip conductor :(
Can you fill me in on how this impacts conductor?
How are they using `claude -p`?
Tell HN: Starting June 15, claude -p usage will change
11–15 of 15 posts
Re: Tell HN: Starting June 15, claude -p usage will change
#12Well 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…
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.
Re: Tell HN: Starting June 15, claude -p usage will change
#13Earlier quoted context omitted.
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.
Re: Tell HN: Starting June 15, claude -p usage will change
#14Earlier quoted context omitted.
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.
Re: Tell HN: Starting June 15, claude -p usage will change
#15[flagged]