docs: analyze Claude sandboxing vs cloud execution approaches

[bborn]

Summary

• Research Claude Code's native sandboxing (bubblewrap on Linux, Seatbelt on macOS) and devcontainer support
• Compare four approaches: native sandbox, devcontainers, Hetzner VPS (current), and Fly.io Machines
• Recommend hybrid approach starting with native sandbox, progressing to containers/VMs as needed

Key Findings

Claude Code Native Sandboxing:

• OS-level filesystem and network isolation
• Works immediately with our existing Hetzner setup
• Enables safe use of --dangerously-skip-permissions
• Minimal implementation effort

Devcontainers:

• Stronger container-based isolation
• Good for per-task isolation
• ~5s startup overhead

Fly.io Machines:

• True VM isolation, ~300ms cold start
• Pay-per-use, scale to zero
• Best for future scaling needs

Recommendation

1. Phase 1 (Immediate): Enable native sandbox on current Hetzner setup
2. Phase 2 (Medium-term): Add devcontainer support for full isolation
3. Phase 3 (Long-term): Evaluate Fly.io for scaling beyond single server

Test plan

• Document created and reviewed
• Future: Implement Phase 1 sandbox config in executor.go

🤖 Generated with Claude Code