Support for local and remote sandboxes in addition to worktrees #60
Description
This seems like a super fun project! Have you considered adding support for local and/or remote sandboxes in addition to git worktrees?
As I'm sure you've already noticed, when you're working on something sufficiently complex the worktree model doesn't scale that well. Either you'll exhaust your local system of resources, or you end up with other resource conflicts like conflicting ports, colliding databases, etc. Especially in codebases that weren't built around local parallelism during development. On top of that, there's also all the security concerns with running agents in YOLO mode on your local machine.
This website makes a good case for why you would want to sandbox things in persisted background environments:
https://background-agents.com/
Local sandboxes, like Boxlite, Docker(-in-Docker), etc, solves for some of this in that one sandbox won't step on the toes of another. Eventually, you're still going to run out of local resources though. And whenever you close your laptop, your agents stop.
Remote sandbox providers like Daytona, E2B, Runloop and platforms like Coder.com let's you solve for the sandboxing in better ways, but lack the DX of local machine development. This project seems to be well situated to bridge that gap.