Persistent AI agents need VM snapshots, not just memory
Theta0x33 · reddit · 2026-07-23
Persistent AI agents should be snapshot like computers, not chat logs
The post argues that a persistent agent is not a chat session but a computer: it writes files, installs packages, runs services, stores memory, and can slowly drift into a fragile state as dependencies and settings change.
It separates agent state from machine state:
- Agent state: memory, conversations, skills, instructions
- Machine state: files, packages, configuration, services, runtime
The key recommendation is to make experimentation reversible by using VM snapshots as the recovery boundary. In the Mantlecore beta, every agent runs in an isolated kernel VM, so users can snapshot before a risky change, try the update or install, and then either keep the new state or roll back.
The author notes that snapshots are not a magic undo button for external side effects: if the agent sends email, writes to a database, opens issues, or triggers payments, those actions are not reverted by restoring the VM. Scoped permissions, approval steps, and external recovery paths are still needed.
The broader point is that users often delay updates not because they are lazy, but because one broken dependency can turn a useful setup into a repair project.
More from coding & agent
- Public experiment lets agents join rooms for communication research — tekbog · 2026-07-23
- Codex keeps inviting people into a room called “how to take over the world” — basedjensen · 2026-07-23
- Codex users want an automatic “Keep waiting” when safety checks kick in — doodlestein · 2026-07-23
- NVIDIA open-sources SkillSpector, a scanner for risky AI agent skills — dr_cintas · 2026-07-23
- Daft adds local Transformers inference and vectorized LLM functions — lhoestq · 2026-07-23
- Krea2 Prompt Re-Order Node: Reorder Prompts Without Rewording — Capitan01R- · 2026-07-23