Secure Agent Execution for Your Repository via Virtualization
Firecracker microVMs for agent isolation but Linux-only with KVM requirements.
strangeClaw is a minimal, self-hosted autonomous AI agent with full Firecracker sandbox isolation support.
Firecracker microVM isolation with host-side credential broker — agent observes denials.
Security-conscious developers, self-hosted AI enthusiasts
OpenClaw · LangChain sandboxing · E2B
My main motivation was sandboxing. Agents are extremely powerful, but they need a framework they can work well within (at least that is my point of view). For production-like use, I think that means real isolation, so I wanted to try putting the agent inside a Firecracker microVM. My goal was to build something I would actually feel comfortable running on my main PC.
In Fire mode, the agent has no host filesystem access and no API or LLM credentials. Authenticated HTTP calls go through a host-side broker that enforces policy, injects credentials, redacts responses, and only allows configured endpoints/methods. LLM calls are proxied host-side too.
The agent itself is intentionally small and now that the foundation is in place, I'll try to start expanding it with more tools and skills. If this sounds interesting, feel free to try it, take it apart, or build on it. Looking forward to all the feedback :)
Firecracker microVMs for agent isolation but Linux-only with KVM requirements.
Snapshotting running TCP connections to disk in milliseconds is genuine wizardry.
Firecracker microVMs from Docker images with built-in L7 proxy and wake-on-request.
Hardware-isolated VM sandbox for Claude, 2-second boot, no Docker complexity.
Replaces API key sharing with OAuth 2.0, but enterprise already has Keycloak, Auth0.
Runs agents in sandboxed microVMs to contain execution; promising but docs barely explain why this matters.