1. Native macOS sandboxing is still missing
Users keep pointing out that the current Docker for macOS runs inside a Linux VM, which is “useful but only as a Linux machine goes.”
- garganzol: “Having real macOS Docker would solve the problem this project solves, and 1001 other problems.”
- mkagenius: “Apple containers were released a few months back… you can use it to completely sandbox Claude code too.”
- xyzzy_plugh: “This is just a wrapper around sandbox‑exec… I wish there was a simple way to sandbox programs with an overlay or copy‑on‑write semantics.”
2. Containers are not perfect security boundaries
The discussion repeatedly stresses that neither containers nor VMs provide absolute isolation, and that sandbox‑exec is a more reliable option for agents.
- dpe82: “Docker containers are not security boundaries.”
- PlasmaPower: “Containers provide a reasonable security/usability tradeoff… the primary concern is kernel vulnerabilities.”
- e1g: “Claude Code has ways to escape its sandbox… Safehouse makes that 0 %, which is categorically different.”
3. Fine‑grained policy and usability matters
Participants highlight the need for easy policy creation, overlay file systems, and a clear “pause‑and‑ask” communication layer for agents.
- xyzzy_plugh: “I do wish that there was a simple way to sandbox programs with an overlay or copy‑on‑write semantics.”
- dbmikus: “We support copy‑on‑write semantics locally… spin up sandboxes from the CLI, expose TCP/UDP ports, and share URLs with teammates.”
- naomi_kynes: “The sandbox keeps the agent contained, but doesn’t give it a clean ‘pause and ask’ primitive… the second layer is still awkward for most setups.”