Roadmap

DevCell is advancing one vertical slice: pair a host, create a cell from a real repository, open it, run services and an agent task, expose a private preview, checkpoint and fork it, then delete everything cleanly.

Golden path available now

• browser-approved host pairing with pinned TLS trust;
• Git repository materialization and deterministic workspace planning;
• Docker/devcontainer startup through the container backend;
• guest exec, fixed workspace-agent tasks, port discovery, and private routes;
• Cursor/VS Code attach through the appliance;
• durable operations, restart reconciliation, checkpoints, sleep, forks, and teardown;
• reproducible NixOS appliance and CellOS build definitions.

Closing the machine boundary

The Firecracker backend already launches real microVM processes and owns TAP, vsock, writable rootfs, jail staging, teardown, and orphan reconciliation. The next integrated release focuses on:

1. staging a freshly built CellOS image with cell-agent listening on vsock;
2. running the same devcontainer golden fixture inside that guest;
3. routing guest services through the existing host port model;
4. adding workspace block checkpoints and fork restore;
5. adding memory snapshots for true suspend and fast resume.

After the single-host loop

Once the dedicated-kernel workflow is reliable, the fabric can expand without changing the basic cell model:

• golden images and prebuilt workspace caches;
• richer scoped credential brokers and policy bundles;
• placement across multiple DevCell Hosts;
• richer agent-task comparison and promotion flows;
• capacity-aware scheduling and checkpoint garbage collection.

The roadmap stays deliberately narrow: DevCell is not trying to become an IDE, source-control system, or public multi-tenant cloud. It is the private runtime and control plane around those tools.