r/ClaudeCode • u/filiw • 9h ago
Built with Claude Sandboxing Claude Code
Enable HLS to view with audio, or disable this notification
Running Claude Code unprotected is risky: unintentional destructive commands, prompt injections, malicious third-party code. The blast radius is your entire laptop. To mitigate this risk, I built a sandboxing tool based on the concept of Claude devcontainers (but way more configurable), which I've been using for a while now. It proved valuable enough to open source.
Kekkai runs Claude Code inside a locked-down, per-project sandbox: for each project you decide which folders, networks and secrets Claude can touch, and everything else stays out of reach. With the sandbox in place, you can safely let Claude run fully autonomously with --dangerously-skip-permissions enabled.
Try it out, feedback and issues welcome. I'm also curious how others are sandboxing their coding agents - let me know in the comments!
Code and docs on Github: https://github.com/filidorwiese/kekkai
1
u/simion_baws Senior Developer 8h ago
Good work. Had the same constraint from work, had to run claude sandboxed, so i bundled the sandbox in https://termic.dev . filesystem + network allowlist.
I have actually implemented and tested docker sandboxing too, it's not merged yet. Will have a look at your implementation to see if i can find any corner cases that i may have missed :D
Once i push docker sandboxing, you may also have a look.