Principle

Separate reusable memory from recoverable session state

A temporary fact may still need to survive a crash. Separate what helps resume this task from knowledge worth reusing across tasks; both may need durable storage.

About 2 min read

Before you use it

Use when
  • A project spans multiple conversations, workers or models.

Keep this limit in mind

  • Some transient-looking events become important evidence after failure; retain raw logs according to audit and incident needs even if they are not promoted into memory.

Current editorial reading

Keep two kinds of continuity

Use session records or checkpoints for the current step, pending decisions and completed tool actions. Keep accepted decisions, terminology and source-linked findings in reusable project memory. Give each store a purpose and retention rule. Do not promote every error into permanent knowledge, but do not discard recovery state just because it is short-lived.

Test the interruption boundary

In a test report workflow, stop the worker after it has read an input file but before reviewing the draft. On restart, check that saved state identifies the file version read and the unfinished review step. Use storage that survives the failure you are testing: an in-memory checkpoint disappears with its process. Restrict access to recovery records and load them only from trusted storage.

Take it with you

A recovery record preserves an observation, not the outside world. Before continuing, check any external state that may have changed; restoring a session does not undo actions already taken.

Sources and evidence (2)

What we checked

Challenges

The cited talk preserves session events for recovery, including tool activity and pending permission decisions; persistence is not reserved for reusable project knowledge.

Direct timestamped transcript passages read; adjacent adapted article is not used as independent corroboration. The distinction between two stores is an editorial design recommendation.

The Log Is The Agent — Ishaan Sehgal, timestamped talk transcript · Transcript 1:32–3:20 and 6:49–7:31

Supports

Workflow checkpoints can retain execution state and pending messages, requests and responses for later resumption.

Official implementation example, not a requirement to adopt Microsoft tooling. The report-recovery example is independently designed; no execution is claimed.

Microsoft Agent Framework Workflows - Checkpoints · Overview; When Are Checkpoints Created?

Limits

In-memory checkpoint storage does not survive process restarts, and checkpoint storage must be trusted and access-controlled.

Selected documentation passages read. The proposed interruption check is designed, not executed.

Microsoft Agent Framework Workflows - Checkpoints · Capturing Checkpoints: provider table and In-Memory; Security Considerations

Limits

A session history does not reverse completed external actions or guarantee that external state still matches an earlier observation.

The talk states this boundary explicitly; no claim of deterministic recovery or zero coordination cost is adopted.

The Log Is The Agent — Ishaan Sehgal, timestamped talk transcript · Transcript 5:41–6:37

Editorial sources (2)

Editorial version 1.0.0 · Evidence checked 2026-10-04

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingSeparate reusable memory from recoverable session state

Original edition evidence and sources

These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.

Supports

Current long-horizon agent practice distinguishes transient working context from durable state that can survive context resets or worker replacement.

A durable log is one architecture; structured snapshots or databases may be better for other systems.

The Log Is The Agent · Durable history, disposable execution

All sources (1)
Original edition, downloads and provenance

The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.

Version 0.1.0

No review details are supplied for this edition.

Read the original edition and overlay as JSON · Release details