Comment by ahmadyan
5 days ago
not yet, just vanilla work-tree, so file isolation. I also poorly manage env isolation through running .agentastic/setup.sh script upon work-tree creation; which can setup .env files, etc.
I wasn't aware of branchbox, i was planning to integrate firecracker in the upcoming version. However Branchbox seems like a great option too.
Which set of container features / isolation matter to you more?
Primarily, I want to run agents with a flag like --dangerously-bypass-approvals-and-sandbox to benefit from newer models' improvements in long-horizon tasks. For that to work, I need solid guarantees it won't rm -rf / my entire system while still allowing full stack access for installing and configuring databases, server daemons, etc. Ultimately that means working within some sort of container and/or VM.
Facilitating long-running tasks makes multiple parallel agents much more compelling.