Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

33% Positive

Analyzed from 182 words in the discussion.

Trending Topics

#claude#impact#acp#reasons#api#guess#xcancel#link#https#com

Discussion (9 Comments)Read Original on HackerNews

stusmall•about 1 hour ago
Does anyone know if this will impact ACP invoking Claude? IE using Claude from zed. I assume not but looking for confirmation
bhu8•about 1 hour ago
It would unfortunately impact it. ACP uses Claude SDK and is developed by a third-party.
TomGarden•about 1 hour ago
This sucks. I use Claude -p over tailscale to code over voice when I’m on the go for accessibility reasons, and most of the time I do the same while at the computer. Running through $200 in API pricing takes no time. Oh well, time to switch providers I guess.
rickdg•about 3 hours ago
Guess we're no short of reasons to stick to Codex.
vova_hn2•about 3 hours ago
XCancel (alternative Twitter frontend) link: https://xcancel.com/ClaudeDevs/status/2054610152817619388

I think that this is much better than the previous situation with total lack of clarity on what is allowed and what isn't.

ChrisArchitect•about 1 hour ago
LoganDark•about 3 hours ago
I use `claude -p` interactively -- I understand why they put it under this new umbrella, but having to open the fullscreen interface each time to not be counted as a programmatic tool is a little disappointing.
StackTopherFlow•about 1 hour ago
The anthropic enshittification continues.
andrewstuart•about 2 hours ago
Can someone explain in plain English please.
martinald•about 2 hours ago
Currently, if you use claude -p (non interactive mode) in for example CI/CD, you can use your included subscription tokens.

They are now changing it to be:

You get $20/$100/$200 of "credit" that can be used for claude -p. Problem is, once you are out of that it is the normal API rates (outrageously expensive).