Running Claude Code dangerously (safely)

Post by pluralmonad » Wed, Jan 21, 2026, 3:14 AM UTC

embedding-shape wrote: post #215

lucasluitjes wrote: post #208

Earlier quoted context omitted.

It's the default behaviour for Vagrant. You put a Vagrantfile in your repo, run `vagrant up` and it creates a VM with the repo folder shared r+w to `/vagrant` in the VM.

That's because Vagrant isn't "VM", it's a developer tool you use locally that happens to use VMs, and it was created in a era where 1) containers didn't exist as they do today, 2) packaging and distribution for major languages wasn't infected with malware and 3) LLM agents now runs on our computers and they are kind of dumb sometimes and delete stuff. With new realities, new workflows have to be adopted. Once malware…

Post by eli » Wed, Jan 21, 2026, 4:30 AM UTC

dist-epoch wrote: post #175

eli wrote: post #153

Earlier quoted context omitted.

Or just a VM that doesn't share so much with your host. Just makes for a more annoying dev experience.

Why do you need to share anything? Code goes through GitHub - VM has it's own repo clone, if you need data files, you mount them read-only in the VM, have a read-write mount for output data.

Post by odie5533 » Wed, Jan 21, 2026, 6:12 AM UTC

thenaturalist wrote: post #163

odie5533 wrote: post #145

I use Development containers (dev-containers) as demonstrated by Claude Code's docs https://code.claude.com/docs/en/devcontainer It all integrates nicely with VS Code. It has a firewall script and you spin up your database within the docker compose file so it has full access to a postgres instance. I can share my full setup if anyone needs it.

This would be lovely and much appreciated! Devcontainers look perfect but also like a bit of a burden to entry with regards to setup.

Post by TZubiri » Wed, Jan 21, 2026, 7:42 AM UTC

crabmusket wrote: post #21

What is the consensus on Claude Code's built-in sandboxing? https://code.claude.com/docs/en/sandboxing#sandboxing > Claude Code includes an intentional escape hatch mechanism that allows commands to run outside the sandbox when necessary. When a command fails due to sandbox restrictions (such as network connectivity issues or incompatible tools), Claude is prompted to analyze the failure and may retry the command wit…

Post by runekaagaard » Wed, Jan 21, 2026, 9:01 AM UTC

tptacek wrote: post #196

runekaagaard wrote: post #192

It's impossible to not get decision-fatique and just mash enter anyway after a couple of months with Claude not messing anything important up, so a sandboxed approach in YOLO mode feels much safer. It takes the stress about needing to monitor all the agents all the time too, which is great and creates incentives to learn how to build longer tasks for CC with more feedback loops. I'm on Ubuntu 22.04 and it was surpris…

I've been working for the past several weeks in an environment where it's easy and safe to give different claudes yolo-mode, but yesterday I needed to build an Emacs TRAMP plugin, and I had to do that on my local development NUC. I am extremely spoiled for yolo-mode, because even just yes-ok'ing all the elisp fragments claude came up with was exasperating, the whole experience was draining, and that was me not being…