Capture a point in context.

A snapshot is a record

A context snapshot captures selected runtime state and source anchors. It is not a backup of every source, an entire model conversation or the running process.

Use the CLI’s snapshot help to inspect the supported actions:

lean-ctx snapshot --help

Inspect before restoring

List the available snapshots, inspect the selected record and verify its integrity before a restore. A valid signature or digest establishes an integrity relationship; it does not establish that the record is appropriate for the current task.

Compare the referenced source revision with the working tree. Source files, permissions and configuration may have changed.

Understand restore scope

Restoring context state and checking out source code are different operations. Review the command’s actual restore behavior and any changes it proposes. Do not assume it restores external data, provider credentials or a host’s conversation.

If a source or artifact cannot be recovered, handle that missing evidence explicitly.

SDK checkpoints are a separate contract

SDK workspaces and checkpoints have versioned records and admission rules that differ from a local runtime snapshot. Use the format and API contract of your installed SDK release; transfer only state that the receiving identity is permitted to use.

Use the SDK guide and its exact release compatibility matrix before building an application around those interfaces.

Sources & versions2 references · Reviewed 17 Sept 2026

• 21-context-time-machine.mddocs/reference/21-context-time-machine.mdGitHub
• snapshot_cmd.rsrust/src/cli/snapshot_cmd.rsGitHub

Core checkout

0ce2207ee4

Installed runtime

3.10.2

SDK release

1.1.0

Separate baselines for source, CLI/configuration and SDK contracts. Review does not certify every platform or integration.

Versions & compatibility