Today we're introducing Cloud Sandboxes: same microVM isolation as Docker Sandboxes on your laptop, same CLI, always-on Docker-managed compute.
Close your laptop. Keep the agent running. Move between local and cloud with one command. $250 credit for new accounts:
Coding agents are most useful on your real repo. A sandbox gives them a safe place to work.
Docker Captain @ghumare64’s latest guide shows you how to isolate agents like Claude Code, set what they can reach, and keep your credentials private.
Every example comes from a real
Happy Halloween. We saved our scariest one for today…
An AI code reviewer, a routine version bump, and a fifteen-hundred-word security report citing a CVE that never existed.
The agent never touched anything. It didn't need to.
Read the full AI Coding Agent Horror story:
AI governance isn't a theoretical problem. It's the credential you said you'd fix later. It's the permission request you approved without thinking. It's the cleanup that wasn't.
How many fingers did you put down? Drop it in the comments.
.@harborframework can now run every eval task in Docker Sandboxes.
This means isolated microVMs, network policies for fair and reproducible runs, and the same setup locally or at scale in the cloud.
Learn more: bit.ly/4knjKNJ
