And Fable is gone too.
Huh?
Auto mode is now the default in Claude Code
111–120 of 338 posts
Re: Auto mode is now the default in Claude Code
#112Earlier quoted context omitted.
A VM hosted by someone else. Somethig on your personal notebook or the proxmox server in your garage is still too risky.
Why are 3rd party hosted VMs safer than your own?
They're not. When things go wrong it's better to compromise someone else's VM host than your own computer. It's only a matter of time now until AI will find novel ways to break out of virtualisation.
Re: Auto mode is now the default in Claude Code
#113What's the current best Mac to buy for offline LLM in used market? I am seeing 96Gb Mac studio 3rd gen I think for a good amount but I guess it would be better than paying for mac mini newer models with lesser ram? Or would it make sense to buy used 32 GB Mac mini 3 or 5? Is there a cost/dollar for various generations which I could compare against used market and pick the most effective one?
Why does it have to be a Mac? Your money probably goes further with a generic PC and Linux?
Re: Auto mode is now the default in Claude Code
#114I've recently been running yolo mode, but in docker container with the codebase I'm working on a as regular mount with other reference code mounted as read only.
I've been experimenting with dedicated Linux users for various external tools with access to the relevant credentials limited to them and the Claude user only able to invoke the relevant clis by going through a pair of wrapper scripts: the first to change user to call the second via a su call as the appropriate user, the second wrapper to invoke a guard script which allows me to implement my own in-code permissions checks against the cli arguments. In _theory_ there's no way for Claude to work around it, as the sudoers file only permits the described manner to change to the user with credentials, and the user with permissions for each credential only ever runs deterministic code.
It's too early days to say how well this second part works out, but so far so good.
Re: Auto mode is now the default in Claude Code
#115It's great that they're making the auto usage tokens free by default and I guess auto mode will be a good default for a lot of workloads, but recent changes to the auto mode classifier just moved me to either use YOLO mode or use a different harness.
I've been using Opus 4.6 for some security related work (it has much looser guardails that later opus models) and last week, all of a sudden, the processes started to fail. It wasn't the main model blocking commands but the auto mode classifier changed how it worked and it started blocking the main models commands.
That's one specific incident, but it does have a wider potential problem which is, if you use Anthropic's harness you'll always be at the risk of sudden breakage from server-side changes that are opaque to the end user, which is a tricky one for building long lasting processes.
Re: Auto mode is now the default in Claude Code
#116Earlier quoted context omitted.
Regarding ulterior motives - these permissions are 'performative' in that anything you can give it permission to do, it already has the ability to do. They're app level - not OS level. So if they wanted to do something, it wouldn't require you to give permission.
The app is split into multiple layers. Just like your browser can do everything already, but only lets websites use specific features.
Right and you rely on that browser to enforce those protections. But if the browser itself was working against you, then the permissions you tell it to give (or not) become meaningless. A good example there is trying to turn off "telemetry" on Windows.
Re: Auto mode is now the default in Claude Code
#117I've been running Claude Code with --dangerously-skip-permissions in a Docker container for the last month or so, allowing me to get up and stretch my legs while it does its thing. I definitely wouldn't want to run it unsandboxed.
same, and unlike other repliers, I'll say one doesn't need to reinvent a new tool for this. Just use devcontainers.
Re: Auto mode is now the default in Claude Code
#118Earlier quoted context omitted.
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.
Boris from the team here. The classifier is free — we do not charge for safety features as a principle.
[deleted]
Re: Auto mode is now the default in Claude Code
#119[flagged]
Re: Auto mode is now the default in Claude Code
#120I'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.
What VM do you run it in?
as context, I build a light weight portable vm designed for this purpose, so genuinely curious.