AI Services Market › Use cases › Software & DevOps
Software & DevOpsDone with Claude Code Oct 20, 2026
Run Claude Code in an isolated VM that opens PRs
The author runs Claude Code in a restricted VM with secrets served from Infisical. It can only create issues and PRs on Forgejo, and merges are manual before CI deploys.
- What They Did
- Claude Code runs in its own VM on a heavily restricted VLAN that can reach only the internet, the author's Forgejo instance, Infisical, and one-way SSH from the author's machine. Secrets come through Infisical, so the agent never sees them. Its Forgejo user can only create issues and PRs. The author merges manually, then CI packages and deploys to an app server VM.
- How It Went
- The source gives no measured results. It describes the setup as overkill but worth it to cut the risk of personal data exfiltration. Dev mode can still expose some secrets locally.
- Worth Knowing
- In local dev mode the agent may still see secrets, so the Infisical protection only fully holds outside that mode.
Try it yourself with Claude Code
Help me set up a locked-down virtual machine for running you on my project [repo name]. Give it only the permissions it needs: reading the code, getting secrets from [secrets manager], and opening issues and pull requests on [Git host], with no ability to merge. Walk me through the setup step by step, and finish by having it open a small test pull request. Pause and show me each command that changes my system or credentials before you run it.
Do this with a skill.
These AI Services Market playbooks do this exact job.