New Claude Code programmatic usage restrictions

(twitter.com)

26 points | by martinald 2 hours ago

9 comments

  • TomGarden 13 minutes 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.
  • stusmall 9 minutes ago
    Does anyone know if this will impact ACP invoking Claude? IE using Claude from zed. I assume not but looking for confirmation
    • bhu8 3 minutes ago
      It would unfortunately impact it. ACP uses Claude SDK and is developed by a third-party.
  • kreidema 3 minutes ago
    This is annoying because tools like conductor use the SDK. So this will either be the end of conductor for me or I switch to codex. Interesting dilemma.
  • rickdg 1 hour ago
    Guess we're no short of reasons to stick to Codex.
  • vova_hn2 2 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.

  • LoganDark 1 hour 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.
  • ChrisArchitect 31 minutes ago
  • StackTopherFlow 41 minutes ago
    The anthropic enshittification continues.
  • andrewstuart 1 hour ago
    Can someone explain in plain English please.
    • martinald 1 hour 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).