forkspace

Forkspace solves a mundane problem that compounds fast: running several copies of the same dev stack side by side without them fighting over ports, containers, and volumes. It leans on a capability Docker Compose already has — project namespacing — and wraps it in a CLI that makes creating and destroying isolated environment “lanes” a one-liner. Three concurrent test lanes running the same stack with zero interference was the proof point.

The reason it’s getting renewed attention is agents. Parallel coding agents need parallel environments, and namespace-per-agent is the natural isolation model. Forkspace is being migrated onto a clfly command tree, which does double duty: it’s the migration case study for clfly’s strangler-fig story, and it makes namespace create/destroy agent-callable over MCP — each agent gets its own filesystem jail and its own stack, provisioned through the same tool surface a human would use.

forkspace up dev
forkspace up test --fork agent-a
forkspace down test --fork agent-a

Roadmap

• up / down / --fork with port allocation
• Per-service isolation levels + export templates
• Lifecycle hooks (bootstrap, seed, teardown)
• Broader host-port probing polish
• Docs pass for multi-repo workspaces