Repository to workspace
Clone a real Git repository, resolve its devcontainer, and start the workspace through one lifecycle.
DevCell
A private development fabric for humans, IDEs, and coding agents.
Golden path liverepo → cell → IDE · exec · ports · checkpoint · fork
Your code gets a machine. Your laptop keeps its boundaries.
Open a repository as a disposable, remotely managed workspace.
DevCell turns project configuration into a durable cell: a workspace you can pair with, open in an IDE, hand to an agent, expose privately, checkpoint, fork, and destroy through one typed control plane.
01PairTrust your DevCell Host
02CreateClone and plan the repo
03WorkIDE · terminal · agent · ports
04BranchCheckpoint · fork · destroy
Open with your tools
Attach Cursor or VS Code, run commands, launch an agent task, and discover project services.
Fork the environment
Checkpoint workspace state and create an independent cell for risky changes or parallel work.
A deliberate trust boundary
Let powerful tools work without giving them the host.
Repository code and agents run on the workload side. The DevCell Host retains authority over identity, credentials, routing, storage, and lifecycle—and records every long-running change.
Read the security model →clients
Swift app · CLI · IDEhost
celld · policy · operation ledgercell
Firecracker · CellOS · cell-agentproject
devcontainer · services · agentThe presentation path
From public Git repo to a live Cursor workspace.
The appliance clones the repository, resolves its workspace, starts the runtime, and returns a stable cell identity. From there, tools use the same API for exec, ports, checkpoints, and forks.
$ devcell cell create \
--name lattice\
--repo github.com/willmortimer/lattice
cellcell_01K…
$ devcell cell start cell_01K…
$devcell cell open cell_01K... --ide cursor --open
workspace/workspaces/lattice
Under the hood