Live data from Hacker News

Running Claude Code dangerously (safely)

blog.emilburzo.com

221–230 of 265 posts

Re: Running Claude Code dangerously (safely)

#221

Bit of a wider discussion, but how do you all feel about the fact that you're letting a program use your computer to do whatever it wants without you knowing? I know right now LLMs aren't overly capable, but if you'd apply this same mindset to an AGI, you'd probably very quickly have some paperclip-maximizing issues where it starts hacking into other systems or similar. It's sort of akin to running experiments on con…

Programs can’t want things, it’s no different than running any other program as your user

It's different in the sense that LLMs are unpredictable and if you let them take arbitrary actions you don't know what's gonna happen, unlike any other program. A random generator doesn't "want" anything but putting it in control of steering my car is a bad idea.

Re: Running Claude Code dangerously (safely)

#223

Earlier quoted context omitted.

What is the advantage of using VMware Workstation Pro for this as opposed to using WSL2?

I think it has default access to your c drive via a mount, for one. You could add layers/sandboxes, but it’s not isolated.

Yeah, I do most Linux stuff on Windows in containers using podman leveraging WSL2, but that's a good point.

Re: Running Claude Code dangerously (safely)

#224

Once approval fatigue and ongoing permission management kicks in, the temptation is strong to run `--dangerously-skip-permissions`. I think that's what we all want - run agents in a locked-down sandbox where the blast radius of mistakes and/or prompt injection attacks is minimal/acceptable. I started running Claude Code in a devcontainer with limited file access (repo only) and limited outbound network access (allowl…

I wanted to vibe code an app in an evening with some friends including setting up coolify for production and testing environments. Ended up with giving Claude root access to a cluster of servers. Vibe coded the entire application with 3 people. Did not touch a line of code. The only shell command given was claude. It spend couple hours to self configure the system. Result was remarkable good. Amazing how far we are already in the ai race.

Re: Running Claude Code dangerously (safely)

#225
post #190

On a pro plan. Use opus 4.5 with thinking enabled. I find that two sessions eats through my entire five-hour "session limit", so no need for parallelization because I've consumed my tokens before I can even blink. I see the power and am considering Max but 5x cost is difficult to swallow. Just doing this for a lark, not professionally.

I have 2 max accounts and still hitting the limits almost daily. Vibing 3 projects simultaneously.

Re: Running Claude Code dangerously (safely)

#226
post #206

Earlier quoted context omitted.

For Windows a quick win is to install VMware Workstation Pro (which is free) and install Ubuntu 24.04 LTS as a VM. Broadcom bought VMware then released Workstation Pro for free and I don't think they kept the download link but you can get from TechPowerUp: https://www.techpowerup.com/download/vmware-workstation-pro/ You can then let LLMs on YOLO mode inside it.

Windows has the WSL for native Linux vms, these days (and also the past ~decade)

I can rm -rf Windows files from WSL2. And so can LLMs.

Meanwhile a VM isolates by default.

Re: Running Claude Code dangerously (safely)

#227
post #25
post #17

I have been running two or three Claude’s bare metal with dangerously skip permissions all day every day for two months now. It’s absolutely liberating.

Until it decides to delete your home directory: https://old.reddit.com/r/ClaudeAI/comments/1pgxckk/claude_cl...

Is it worth the risk? For me yes. Today Claude decided to checkout a git commit from yesterday and all local unstaged changed were lost. Annoying mistake. Lost 6 hours of work I think. Nevertheless I still prefer giving all access to Claude. Also root. It can do everything.

Re: Running Claude Code dangerously (safely)

#228
Hmm... I'm relatively new, but I've been using utility scripts in a run/ directory in my project that will spin up containers based on compose, and that includes dev containers volume mapped to my host directories in a given project. It's worked pretty well for me at least. Similar to TFA, it's been able to configure services in the compose file, update the utility scripts and diagnose problems in the services in runtime and dev modes respectively. No browser integration though, but I'm sure playwright/puppeteer work.

Re: Running Claude Code dangerously (safely)

#229

Earlier quoted context omitted.

What is the advantage of using VMware Workstation Pro for this as opposed to using WSL2?

I think it has default access to your c drive via a mount, for one. You could add layers/sandboxes, but it’s not isolated.

Funny, but I wrote some environment initialization and setup scripts that you just unzip to a new dev desktop, and run the first powershell script, and it will work through (have to reboot after a couple installs), but it goes through, then once WSL is up, it'll rely on the /mnt/c/ paths to run bash scripts to initialize the wsl environment too... was pretty handy.
Post reply on HN