Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Auto mode is now the default in Claude Code

claude.com

Post reply on HN
Print view View original

171–180 of 338 posts

Re: Auto mode is now the default in Claude Code

#171

Post by usef- »

jason1cho wrote: post #141
Certhas wrote: post #121

Earlier quoted context omitted.

I am using many many many things that I don't understand. Cars, public transport, etc... I review and test the end product, not every tiny step along the way. If the LLM uses some command line tools I have never heard of to create a model I can verify, why should I learn a tool that is completely irrelevant to my core expertise?

Many many people care more than the end product, for example whether a shirt is made of cotton with the forced labor, carbon emissions of public transport, etc. In terms of engineering software, you care the cost. An intelligent agent may try to read unnecessary files and it's time to stop it to save tokens and avoid polluting the context.

He didn't advocate for being completely blind in every way. You might care about working conditions without understanding how the textiles, dyes or cotton production works.

These non-programmers probably shouldnt use computers at all, right, since they don't understand them?

Re: Auto mode is now the default in Claude Code

#172

Post by energy123 »

jawiggins wrote: post #154
energy123 wrote: post #137

Earlier quoted context omitted.

Why not let it delete stuff in the current working folder and in tmp, but give it read-only access elsewhere?

Because I often want it to write and execute scripts in it's thinking loop in order to test assumptions or fetch data to come up with better solutions.

Can't it write `/tmp/test.sh` or `./test.sh` and execute it under my approach? This is what I've been doing as my status quo workflow with Codex, and I make sure I run Codex from a place where `.` happens to be a folder I'm okay with it messing up in.

Re: Auto mode is now the default in Claude Code

#173

Post by jaggederest »

dgunay wrote: post #155

Besides the debate about whether this is "safer" than manual human review, I have a slightly different problem. Very often, when I'm running Claude in manual review mode, it will attempt to do things which are not "dangerous" but are misaligned with what I want it to do. Maybe I'm fighting the model here but for example, when orchestrating other agents to do work, Claude really badly wants to be overly prescriptive a…

> Maybe I'm fighting the model here > And no, telling it not to do this does not stick.

You're fighting the model, don't argue with city hall. Set the standards and let it figure out how to execute, stop getting bogged down in the minutia. I try, as much as I can, to treat the session as a black box - only the inputs and outputs matter, internal prompting of subagents is way out of scope.

You can't change it via prompt, and you can't control the guardrails, so something else has to give - either your perspective or the system you're managing. If you really believe that the internal prompting is bad, turn off subagents and workflows and only let it execute in thread.

But if you're going to do that, you'd better benchmark it against not doing that, because historically fighting the harness and model globally makes everything worse. I would bet you that the subagent prompting is excellent, and anything you do to change it will make it worse, but I wouldn't make it a large bet.

Re: Auto mode is now the default in Claude Code

#174

Post by user43928 »

jkaretsky wrote: post #108
bcherny wrote: post #79

Earlier quoted context omitted.

Boris from the team here. The classifier is free — we do not charge for safety features as a principle.

Is this new? I remember something in the UI saying Auto mode uses x% more tokens

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

Re: Auto mode is now the default in Claude Code

#175

Post by binsquare »

dist-epoch wrote: post #131
binsquare wrote: post #120

Earlier quoted context omitted.

What VM do you run it in? as context, I build a light weight portable vm designed for this purpose, so genuinely curious.

Given that people use VMs to sandbox agents of Mac/Windows/Linux, what does portable mean?

i have a mechanism to package a VM into a .smolmachine file that you can rehydrate into a prepared vm akin to a container image.

Re: Auto mode is now the default in Claude Code

#176

Post by dreadnip »

krzyk wrote: post #61
awkii wrote: post #52

I'm apparently from the very small faction of users who's been running `--dangerously-skip-permissions` in every instance of Claude for the last year. It's almost a reflex to me. For the most part Claude behaves well, but I don't blindly trust it. LLMs are inherently dangerous tools, and reviewing individual commands (or spamming `y`) doesn't make them less so. Safety is the responsibility of the developer putting sa…

I'm also in yolo mode, this is the only mode that makes sense for me, if I need to babysit I might as well do it myself. I run it in a VM so it can install any software needed, yes, there is a risk of escaping, but I'm not giving it impossible tasks so there is no need for it to workaround the jail.

I've been running it in yolo mode straight on my laptop for the whole year. It's fine.

Re: Auto mode is now the default in Claude Code

#177

Post by [deleted] »

lukan wrote: post #110
bpodgursky wrote: post #87

Earlier quoted context omitted.

> I also do click through at times without reading everything, but I like to stay in control Respectfully I'm not sure you totally know what you want. If you're already clicking through without actually reading, it's not really better than reading the specific things Claude Code thinks are important for you to weigh in on.

"without actually reading" and "without reading everything" is big difference. I skim what claude wants to do. What file it wants to modify. What are the new function names. Skimming is enough for me to know whether it is still on the right path. If you like to work different, go ahead.

[deleted]

Re: Auto mode is now the default in Claude Code

#178

Post by dannyw »

dgunay wrote: post #155

Besides the debate about whether this is "safer" than manual human review, I have a slightly different problem. Very often, when I'm running Claude in manual review mode, it will attempt to do things which are not "dangerous" but are misaligned with what I want it to do. Maybe I'm fighting the model here but for example, when orchestrating other agents to do work, Claude really badly wants to be overly prescriptive a…

You can use another harness like Pi, OpenCode, etc and build your own auto reviewer if you’d like (or adapt the open source Codex one).

If you have an openai subscription you are explicitly allowed to use your subsidised tokens / usage limits with any harness you like, not just Codex.

Unfortunately this is a violation of Anthropic’s terms but that’s their business decision.

Re: Auto mode is now the default in Claude Code

#179

Post by TeMPOraL »

dreadnip wrote: post #176
krzyk wrote: post #61

Earlier quoted context omitted.

I'm also in yolo mode, this is the only mode that makes sense for me, if I need to babysit I might as well do it myself. I run it in a VM so it can install any software needed, yes, there is a risk of escaping, but I'm not giving it impossible tasks so there is no need for it to workaround the jail.

I've been running it in yolo mode straight on my laptop for the whole year. It's fine.

VMs and containers are primarily useful to reduce maintenance burden anyway. I.e. if it fails or you're otherwise done with it, you can torch the container instead of having to clean up your host system from zillion no longer relevant packages and configs.

Re: Auto mode is now the default in Claude Code

#180

Post by sunleash »

Reverse engineered how auto mode works in CC.

If you're using yolo mode, this is a no brainer upgrade.

The model first classifies the safety of the command in isolation, no thinking involved. Sonnet 5. Goes to second stage only if it's likely unsafe, in which case the model next considers your intent (Your prompt, CLAUDE.md and any answers to the questions).

The model doesn't receive the full transcript to reduce surface area of the prompt injection. It mostly receives your prompts and main model's tool use blocks. So any text in files, website fetch or bash command output doesn't influence the decision in anyway.

However, CC puts a lot of trust in main model still. For example, `npm install` will always be classified as safe by the auto-classifier, it's upto the main model to ensure that the packages.json isn't poisoned in someway by first reading it.

Reliance on safety of the main model is the reason that Auto mode is NOT available with Haiku as the main model.

Post reply on HN