Skip to content
Sessions

Run your agent in a recoverable session.

KeepState hosts your agent's working environment and checkpoints it, so a supported recovery can resume from the last saved point.

Scope and operating details

KeepState hosts the agent's working environment. A checkpoint captures the documented guest state so a supported recovery can resume from that point. Recovery starts from a saved checkpoint, not from every unsaved change. Provider-held state and external side effects have separate boundaries.

RunA recoverable agent session
SaveA checkpoint of session state
ContinueResume the saved session
Illustrative workflow. The evidence and limitations below define the tested scope.

filesystem

+

process memory

+

tool state

one atomic checkpoint

Filesystem, process memory, and tool state are captured in one write, so a restore returns them from the same point in time. Provider-side KV cache is not ours to freeze; what survives is the agent's own memory and world.

A session is a micro-VM we can freeze. The freeze is one write, not three: if the filesystem were captured at t and the process memory at t plus 40 ms, the agent would wake remembering a file that does not exist. (The 40 ms is an illustration of skew, not a measurement.)

Storage is content-addressed: 82 checkpoints of one soak occupied 4,233 MiB against 80,952 MiB naive, a 19.1x dedup, measured once, on one workload. That is why the cadence can be aggressive enough to make a crash boring.

MEASURED, bench

Historical bench result · editorial summary Historical bench recording
29 July 2026 · laboratory demonstration
An agent session was checkpointed and hard-stopped.
The saved session resumed; observed downtime was 25.2 seconds.
One demonstration, not a recovery-time guarantee.

An editorial summary of a historical result, not a session running now. Dates, scope and limitations are on the walkthrough.

a conversation, not a self-serve step

Book a supervised interruption demo: you type the kill on our bench.

A 30-minute call where you type the kill -9 yourself and watch the session come back with its work intact.

Ask about a recovery walkthrough

RAM-only guest resume

1.50-1.65 s MEASURED

measured across soak cycles

evidence
badge
MEASURED
measurement
1.50-1.65 s · measured across soak cycles
test scope
Laboratory or bench evidence; production behavior is not inferred from it.
date
31 July 2026

Agent session resume

13.7-25.2 s MEASURED

measured (gates 4, 6, 7). No second region exists, so no cross-region number does either.

Kill-and-resume

25 / 25 MEASURED

fresh cycles, Wilson 95% CI [86.7%, 100%]. The claim is the interval, not the point.

evidence
badge
MEASURED
measurement
25 / 25 · fresh cycles, Wilson 95% CI [86.7%, 100%]. The claim is the interval, not the point.
test scope
Laboratory or bench evidence; production behavior is not inferred from it.
date
31 July 2026

Dated public summaries retain the measured resume latency, tested environment and durability limits. record

Try a recoverable session.

Create an account, bring a model key, and follow the hosted quickstart.

keepstate.ai · the durable agent session cloud