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

Running Claude Code dangerously (safely)

blog.emilburzo.com

Post reply on HN
Print view View original

11–20 of 265 posts

Re: Running Claude Code dangerously (safely)

#11

Post by vidarh »

letmetweakit wrote: post #9

I run Claude in a Proxmox VM, generally the experience has been great. In my experience it also behaves better than gemini cli, that likes to create files all over the place if set loose (lesson learned to add that requirement to the relevant .md files)

Something that contains Claude even more in this respect is if you explicitly gives it a directory that you tell it is entirely under its control, and tells it to write md files and other intermediate work products there (and this seems to work better than telling it where it isn't allowed to leave things).

Re: Running Claude Code dangerously (safely)

#14

Post by emilburzo »

letmetweakit wrote: post #9

I run Claude in a Proxmox VM, generally the experience has been great. In my experience it also behaves better than gemini cli, that likes to create files all over the place if set loose (lesson learned to add that requirement to the relevant .md files)

This was also the direction I was initially headed, but then I realized I wanted one-VM-per-project so it can really do anything it wants on the complete VM. So the blast-from-the-past-Vagrant won because of the Vagrantfile + `vagrant up` easiness.

Re: Running Claude Code dangerously (safely)

#15

Post by scalemaxx »

letmetweakit wrote: post #9

I run Claude in a Proxmox VM, generally the experience has been great. In my experience it also behaves better than gemini cli, that likes to create files all over the place if set loose (lesson learned to add that requirement to the relevant .md files)

In installed Gemini as an extension in VS Code and it kept wanting to index all my files. Still trying to figure out what it was doing outside of the VS Code folder I had set it to work on.

Re: Running Claude Code dangerously (safely)

#16

Post by emilburzo »

tobyhinloopen wrote: post #6

How about running Claude as a different user with very limited permissions?

I tried this approach for a while, but I really wanted it to be able to do anything (install system packages, build/run Docker containers, the works).

With these powers there's a lot less back-and-forth with me running commands, copying the output, pasting it to Claude, etc.

I'm sure you've had the case where you had to instruct someone to do something (e.g. playing tech support with family, helping another engineer, etc). While it helps the other person learn, it feels soooo slow vs just doing it yourself :) And since I don't have to teach the agent, I think this approach makes sense.

Re: Running Claude Code dangerously (safely)

#18

Post by progval »

gregoriol wrote: post #8
tobyhinloopen wrote: post #6

How about running Claude as a different user with very limited permissions?

This breaks the non-interactive mode the post want to achieve. Claude will not be able to install some things and will require user action, which is not desired here.

Like what? It can already use npm/pip/etc. And if it needs a new APT package or config in /etc/ then you would want to know because you need to document it.

Re: Running Claude Code dangerously (safely)

#19

Post by letmetweakit »

emilburzo wrote: post #14
letmetweakit wrote: post #9

I run Claude in a Proxmox VM, generally the experience has been great. In my experience it also behaves better than gemini cli, that likes to create files all over the place if set loose (lesson learned to add that requirement to the relevant .md files)

This was also the direction I was initially headed, but then I realized I wanted one-VM-per-project so it can really do anything it wants on the complete VM. So the blast-from-the-past-Vagrant won because of the Vagrantfile + `vagrant up` easiness.

I use Proxmox snapshots to get back to a clean state. I’ll take a look at Vagrant too though.

Re: Running Claude Code dangerously (safely)

#20

Post by tobyhinloopen »

delaminator wrote: post #12
tobyhinloopen wrote: post #6

How about running Claude as a different user with very limited permissions?

I run it with sudo enabled - true story just give it its own machine and let it check out any code I PXE boot it from a known image when I feel the need

Running it remotely on a VM seems like a very sensible option. Just don't give it permission to nuke the remote repository hah (EG don't allow force-push, use protected branches, only allow write access to branches it created)
Post reply on HN