Session Persistence

Pain Signals — You Need This Pattern When:

• A crashed harness loses hours of agent work that cannot be cheaply re-run
• Users want to close their laptop mid-session and resume tomorrow
• Debugging a bad agent run requires replaying it step-by-step
• Operators need an audit trail of every model call, tool call, and decision
• A long-running task should be forkable — explore two approaches from a common ancestor
• Multiple processes (CLI, web UI, scheduled job) act on the same logical session

Sessions are append-only event logs. The in-memory state is a projection of the log. If you cannot reconstruct state by replaying the log, you do not have persistence — you have a cache.

Core Principle