Running Claude Code dangerously (safely)
blog.emilburzo.com
Running Claude Code dangerously (safely)
1–10 of 265 posts
Re: Running Claude Code dangerously (safely)
#2Keeping in mind with Vagrant: if you are using a synced_folder in your host as a source folder in the VM, those files in the synced_folder will be modified on the host.
Re: Running Claude Code dangerously (safely)
#3Keeping in mind with Vagrant: if you are using a synced_folder in your host as a source folder in the VM, those files in the synced_folder will be modified on the host.
Good point. For me, that was intentional, since all my projects are in git I don't care if it messes something up. Then you get the benefit of being able to use your regular git tooling/flows/whatever, without having to add credentials to the VM.
But if you need something more strict, 'config.vm.synced_folder' also supports 'type rsync', which will copy the source folder at startup to the VM, but then it's on you to sync it back or whatever.
Re: Running Claude Code dangerously (safely)
#4Keeping in mind with Vagrant: if you are using a synced_folder in your host as a source folder in the VM, those files in the synced_folder will be modified on the host.
Good point. For me, that was intentional, since all my projects are in git I don't care if it messes something up. Then you get the benefit of being able to use your regular git tooling/flows/whatever, without having to add credentials to the VM. But if you need something more strict, 'config.vm.synced_folder' also supports 'type rsync', which will copy the source folder at startup to the VM, but then it's on you to…
I like this workflow a lot, actually. Docker is great and all, but depending on the project, Vagrant helps "keep it simple".
Thanks
Re: Running Claude Code dangerously (safely)
#5Keeping in mind with Vagrant: if you are using a synced_folder in your host as a source folder in the VM, those files in the synced_folder will be modified on the host.
[dead]
Re: Running Claude Code dangerously (safely)
#6How about running Claude as a different user with very limited permissions?
Re: Running Claude Code dangerously (safely)
#7I'm doing this with a remote VM on exe.dev and it's quite nice. Well, actually with their own coding agent but they have Claude Code preinstalled too.
Syncthing works well for getting a local copy of a directory from the VM.
Re: Running Claude Code dangerously (safely)
#8How 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.
Re: Running Claude Code dangerously (safely)
#9I 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)
Re: Running Claude Code dangerously (safely)
#10Keeping in mind with Vagrant: if you are using a synced_folder in your host as a source folder in the VM, those files in the synced_folder will be modified on the host.
If the folder is versioned and commited regularly there is no problem. It also allows you to open the files in your IDE, do some other tasks or fixes for claude. It prevents claude from accessing any other folder, which is the idea of the post.