One project. One world.
Every project gets its own persistent Firecracker workspace, with a real filesystem and a clean boundary.
A new habitat for software
Fork gives every project an isolated, persistent computer where agents can build, test, and ship—without stepping on your machine or each other.
Persistent workspaces · isolated by design
Agents work inside full, isolated Linux machines—not simulated file trees.
Your code, tools, and context stay put between sessions and deployments.
Fork an entire working world, explore freely, and keep the useful version.
How it works
Every project gets its own persistent Firecracker workspace, with a real filesystem and a clean boundary.
Explore an idea in parallel without destabilizing the main workspace. The experiment gets its own address.
Agent cycles become a legible history of changes, with checkpoints you can inspect, compare, and return to.
Why Fork exists
Agents are more useful when they can inhabit the software they make.
A chat window is a good place to begin. A durable, inspectable computer is a better place to build. Fork keeps the speed of conversation and adds the continuity, boundaries, and control that serious software needs.
Your next workspace is ready