The article questions whether continuity in long-running AI agents should focus on preserving state or maintaining coherence through inevitable change, exploring implications for memory, actions, and interactions.
I’ve been thinking about continuity in long-running AI agents, especially after reading discussions about memory, persistent state, and recovery. We often seem to frame continuity as a preservation problem: ▪︎preserve memory ▪︎preserve context ▪︎preserve state ▪︎preserve identity But I wonder if this starts from the wrong assumption. A long-running agent will inevitably change. Its information changes, its environment changes, its decisions affect the external world, and later evidence may invalidate assumptions that were previously reasonable. Once an agent has acted on the world, simply restoring an earlier internal state may not restore continuity. The world itself is now different. So perhaps continuity is less about preserving sameness and more about remaining coherent through change. Consider three cases. 1. Memory continuity If some memories are lost, compressed, or revised, does the agent necessarily become a different agent? Or can continuity survive partial discontinuity in memory? 2. Action continuity Suppose an agent makes a decision, acts externally, and later discovers that the information supporting that decision was wrong. It cannot always roll the world back. Instead, it may need to trace which later decisions depended on that information, reassess their effects, repair what can be repaired, and incorporate the consequences into its future behavior. In that case, recovery may not simply restore continuity. Recovery may be part of what continuity is. 3. Relational continuity Things become even stranger when agents continuously interact with humans or other agents. Neither side remains unchanged. Each interaction alters the conditions for the next one. Over time, continuity may exist not in a preserved snapshot, but in a trajectory produced through repeated interaction, prediction, correction, and repair. This makes me wonder whether we should think of continuity as a property of a state at all. Perhaps it is closer to a property of transitions between states: not “Did the system remain the same?” but “Can the system incorporate change without losing coherence with the trajectory that produced it?” I don’t think this resolves the identity problem. It probably makes it harder. Because then another question appears: At what point does successful repair count as continuity, and at what point has the trajectory changed enough that we should call it a new system or identity? I’d be especially interested in how people building long-running agents think about this. Is this already captured adequately by existing approaches such as event sourcing, provenance, transactional state, checkpointing, and recovery mechanisms? Or is there something about autonomous agents that makes continuity a distinct systems problem?
Reflects on the continuity problem for long-running AI agents, arguing that a deterministic control layer is needed to manage authoritative state, and questions whether existing infrastructure like IAM, transactions, and provenance is sufficient.
The author reflects on experimenting with custom AI agents, noting that long-term memory and continuity transform them from simple task runners into persistent collaborators with 'stable dispositions'. This raises questions about the value of agent 'personality' versus the need for control, reliability, and auditability in workflows.
The article reflects on the complexities of AI agent memory beyond simple storage, highlighting challenges such as determining truthfulness, priority changes, distinguishing decisions from noise, and appropriate timing for surfacing context.
The article argues that coding agents need continuity—preserving execution history and project state in the repository—rather than simply larger memory or context windows, to avoid losing the operational thread between sessions.