Amika lets coding agents keep their VMs between pull requests
Founder Dylan Mikus argues reusable VMs preserve state across related agent tasks, while Amika still supports isolated per-task machines.
By Ryan Merket · Published
Primary source: X
Why it matters
Agent infrastructure is moving beyond one disposable sandbox per task. Persistent workstations can preserve useful state, but they make identity, secrets and VM lifecycle controls central product requirements.
Dylan Mikus (@dbmikus), co-founder and CEO of Amika, argued in a September 13th thread on X that cloud coding agents should be able to reuse persistent virtual machines rather than rebuild a clean environment for every pull request.
"Forcing cloud agents onto ephemeral VMs is wrong," Mikus wrote. His case centers on setup and continuity: agents often need repositories, credentials, development services, caches and temporary files that take time to reconstruct and may never be captured in the codebase.…
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.