4 ms·

Worth mentioning as I think at least a few of the commenters are mixing them up: auto mode is different from --dangerously-skip-permissions / YOLO mode. In auto

Worth mentioning as I think at least a few of the commenters are mixing them up: auto mode is different from --dangerously-skip-permissions / YOLO mode. In auto mode, there's a classifier that runs before any command is executed and theoretically blocks any dangerous commands from running. I've found it to be quite annoying and overly zealous, but probably pretty effective.

w29UiIm2Xz 2mo ago
Claude seems to waste a lot of tokens internally bickering with itself. As much as organizations are optimizing spend, Claude's product guidance seems to be doing everything to fight against that headwind. When operating in a capped cost environment, engineers will simply get less use out of it.
- sandcat_ 2mo ago
  The classifier runs Sonnet so I doubt it contributes too much.
- bcherny 2mo ago
  Boris from the team here. The classifier is free — we do not charge for safety features as a principle.
  - adastra22 2mo ago
    That’s good to know, thank you.
  - jkaretsky 2mo ago
    Is this new? I remember something in the UI saying Auto mode uses x% more tokens
    - user43928 2mo ago
      Yes, it's in the article: > The auto mode classifier uses a small number of extra tokens per tool call, and we're no longer charging Claude Code users on Pro, Max, and Team plans for that classifier overhead, effective today
      - jmholla 2mo ago
        That's a bit difference that Boris's claim that they don't charge for this as a "principle".
      - kevincox 2mo ago
        This just sounds like they bump their unspecified limits by N% to cover this usage. Which of course means nothing because the next time they re-evaluate their limits they will just ignore this bump.
  - deleted 2mo ago
    [deleted]
Fishkins 2mo ago
> theoretically blocks any dangerous commands from running To be more precise, this article says auto mode blocked 89% of dangerous commands in their testing. A previous article[0] said it blocked 83%, but presumably it improved since then. 0: https://www.anthropic.com/engineering/how-we-contain-claude https://www.anthropic.com/engineering/how-we-contain-claude

w29UiIm2Xz 2mo ago

Claude seems to waste a lot of tokens internally bickering with itself. As much as organizations are optimizing spend, Claude's product guidance seems to be doing everything to fight against that headwind. When operating in a capped cost environment, engineers will simply get less use out of it.

sandcat_ 2mo ago
The classifier runs Sonnet so I doubt it contributes too much.
bcherny 2mo ago
Boris from the team here. The classifier is free — we do not charge for safety features as a principle.
- adastra22 2mo ago
  That’s good to know, thank you.
- jkaretsky 2mo ago
  Is this new? I remember something in the UI saying Auto mode uses x% more tokens
  - user43928 2mo ago
    Yes, it's in the article: > The auto mode classifier uses a small number of extra tokens per tool call, and we're no longer charging Claude Code users on Pro, Max, and Team plans for that classifier overhead, effective today
    - jmholla 2mo ago
      That's a bit difference that Boris's claim that they don't charge for this as a "principle".
    - kevincox 2mo ago
      This just sounds like they bump their unspecified limits by N% to cover this usage. Which of course means nothing because the next time they re-evaluate their limits they will just ignore this bump.
- deleted 2mo ago
  [deleted]

Fishkins 2mo ago

> theoretically blocks any dangerous commands from running To be more precise, this article says auto mode blocked 89% of dangerous commands in their testing. A previous article[0] said it blocked 83%, but presumably it improved since then. 0: https://www.anthropic.com/engineering/how-we-contain-claude https://www.anthropic.com/engineering/how-we-contain-claude