Isolating Claude Code
yieldcode.blog
Isolating Claude Code
1–4 of 4 posts
Re: Isolating Claude Code
#2What I was also curious about is what is actually sent and received by the agent, so I included this feature and created a CLI to make integration easier in a developer workflow.
Since I started doing this for other agents as well, I considered the idea of using a VM with Vagrant. However, I want the setup to remain minimal, so I still believe there is room for improvement.
Re: Isolating Claude Code
#3I also had the same idea when I built https://github.com/nezhar/claude-container . What I was also curious about is what is actually sent and received by the agent, so I included this feature and created a CLI to make integration easier in a developer workflow. Since I started doing this for other agents as well, I considered the idea of using a VM with Vagrant. However, I want the setup to remain minimal, so I still…
Re: Isolating Claude Code
#4I also had the same idea when I built https://github.com/nezhar/claude-container . What I was also curious about is what is actually sent and received by the agent, so I included this feature and created a CLI to make integration easier in a developer workflow. Since I started doing this for other agents as well, I considered the idea of using a VM with Vagrant. However, I want the setup to remain minimal, so I still…
I found VM to be on-par with Docker. Sure, the initial provision takes time, but this is true to for initial Docker build as well. I know that worrying about sharing kernel with the Docker container, is probably light paranoia, but I really don't trust agents to not run malicious code.
I'm not sure how large the image becomes on the VM or if the distribution process is straightforward.