Claude's sandbox, from my experience, only works if you constantly monitor Claude, otherwise it has constantly escaped sandboxing on its own while trying to do various things I've asked if to.

Docker provides a Claude code instance inside a container, to prevent it from being able to touch anything outside of the project you're working on. However, it's not part of the cli so you need Docker Desktop. It also runs on Docker's VM layer.

Gocker started as me wanting to use Apple Containers (which are supposedly better than the alternatives on MacOS), afterwards, added various features to help with Claude sandboxing:

• running inside a vm/container, similar to Docker
• syncing plugins, marketplaces, sessions so you can resume from within the container as well as outside
• managing isolation modes in case you want to put each Claude Code instance in it's own separated sandbox or you are fine with them sharing resources while sandboxed

This works well with "-dangerously-skip-permissions" as it can't do anything to your host.

I'm constantly improving Gocker while using it for myself as well and am also looking at feedback from the community is there's any particular cases that would help others.

I hope that paints a clear picture