Run persistence
Persisted run event history, summaries, and conversation restoration.
Run persistence
The daemon persists each run as an event timeline under its configured runs directory. This replaces the previous working-directory-based session store: persistence is now keyed by run ID, so a run keeps the same identity when it is loaded or continued.
RunOverview
Summary information returned when listing saved runs.
Prop
Type
RunStore
The interface used to append events and retrieve saved run history.
Prop
Type
Persisted event history
Each run is stored as newline-delimited timeline events. Events record the run's configuration, human inputs, agent calls, conversation retention changes, and final status. getEvents(runId) returns the parsed timeline in append order.
Use listRuns() to retrieve run summaries without loading every timeline. Use getEvents(runId) when you need the full event history for a specific run.
Conversation restoration
When you prepare a completed run for continuation, the run system rebuilds its conversation from the saved timeline. Human prompts remain distinct from inter-agent messages, and retained agent context is restored before the continuation begins.
Saved configuration provides the strategy path, working directory, project manifest, and model override for a continuation. Values supplied during preparation override their saved equivalents.
Deleting a run
Calling deleteRun(runId) removes the persisted timeline for that run. Active execution state is separate; stop an active run before deleting its saved history.
See Run system for the continuation lifecycle and List and subscribe for client-facing run discovery.