[sroussey]

Do people really run claude and other clis like this outside a container??

[kenforthewin]

Let's not fool ourselves here. If a security feature adds any amount of friction at all, and there's a simple way to disable it, users will choose to do so.

[Fishkins]

I'm sure most folks run Claude without isolation or sandboxing. It's a terrible idea, but even most professional software developers don't think much about security.

There many decent options (cloud VMs, local VMs, Docker, the built-in sandboxing). My point is just that folks should research and set up at least one of them before running an agent.

[kelnos]

Yes. I don't bother with that. I feel like the risk of Claude Code running amok is pretty low, and I don't have it do long-running tasks that exceeds my desire to monitor it. (Not because I'm worried about it breaking things, it's just I don't use the tool in that way.)

[matheusmoreira]

How did you contain Claude Code? Did you virtualize it? I just set up a simple firejail script for it. Not completely sure if it's enough but it's at least something.

[arcanemachiner]

The official Claude Code repo is configured use a devcontainer config:

https://github.com/anthropics/claude-code

You can download the devcontainer CLI and use it to start a Docker container with a working Claude Code install, simple firewall, etc. out of the box. (I believe this is how the VSCode extension works: It uses this repo to bootstrap the devcontainer).

Basic instructions:

- Install the devcontainer CLI: `https://github.com/devcontainers/cli#install-script`

- Clone the Claude Code repo: `https://github.com/anthropics/claude-code`

- Navigate to the top-level repo directory and bring up the container: `devcontainer --workspace-folder . up`

- Start Claude in the container: `devcontainer exec --workspace-folder . bash -c "exec claude"`

P.S. It's all just Docker containers under the hood.

[stefans]

I‘m using https://www.docker.com/products/docker-sandboxes/

Better isolation than running it in a container.