Open-source coding agent octomind chooses persistent cloud machines over per-session sandboxes
donk8r · reddit · 2026-07-23
Persistent machines vs. ephemeral sandboxes for long-running coding agents
The team behind octomind, an open-source coding agent, says they moved to persistent machines in the cloud instead of rebuilding an ephemeral sandbox for every session.
Their reasoning:
- Pros: warm code index and memory, long-running tasks survive laptop closures, and the environment can evolve like a real dev machine.
- Cons: higher cost while active and, more importantly, environment drift.
To reduce nondeterminism, they preinstall a known-good image containing the agent, code index, memory, and Docker. But they still lack a fully locked versioning model once users upgrade beyond that image.
Because the project is bootstrapped and invite-only while they buy hardware, they’re asking others how they handle long-lived agents in practice: persistent boxes or rebuild-per-session, and how they control drift.
More from coding & agent
- Dev training a guard model to block prompt injection, tool and memory poisoning — gnukeith · 2026-10-27
- SF 'Code Engineering' event picks up where 1,000-person harness engineering meetup left off — LangChain · 2026-10-27
- Prompt turns Claude Code into an iPhone backup forensics tool exposing 30-day 'deleted' photo copies — alex_verem · 2026-10-27
- Prompt turns Claude Code into a forensics tool finding deleted iPhone photos in backups — alex_verem · 2026-10-27
- Phones won't be mobile IDEs but control planes for agent fleets, argues Yuchen Jin — Yuchenj_UW · 2026-10-27
- FrontierCS 2 launches on Kaggle: 48 tasks make agents beat published CS papers — MeganRisdal · 2026-10-27