CLI Command
beam snapshots
List, inspect, and restore local snapshots from previous Beam design fetches.
Snapshots make one-shot Figma access durable. After Beam successfully fetches a frame, the snapshot records source metadata, hash, Beam version, mode, timestamps, and paths to raw payloads, briefs, images, and asset manifests.
beam snapshots list helps users find prior work without hitting Figma again. beam snapshots show explains what data exists, what paths are available, and whether the snapshot can support offline review.
beam snapshots restore materializes snapshot artifacts into local cache locations so inspect, evidence review, export, or agent workflows can continue from stored data.
Snapshot commands should not bypass permissions or pretend stale data is fresh. When using older data, Beam should make cache age and evidence confidence visible.
1beam snapshots list2beam snapshots show <snapshot-id>3beam snapshots restore <snapshot-id>
Run Sequence
- Run
beam snapshots listto see stored design captures. - Run
beam snapshots show <snapshot-id>to inspect paths, age, source URL, and available artifacts. - Run
beam snapshots restore <snapshot-id>when you need offline reuse. - Run inspect again only when you need fresh Figma data.
Expected Output
list should show snapshot ids, frame names or source URLs, creation time, mode, and artifact availability. show should expose paths without printing secrets.
Files And Artifacts
- .beam/cache/snapshots/<snapshot-id>.json
- .beam/cache/briefs/<snapshot-id>.json
- .beam/cache/images/<snapshot-id>.png
Next Step
Use restored snapshot artifacts with inspect, export, MCP tools, or compare.
Recovery Paths
- If a snapshot is stale, rerun inspect with live Figma access.
- If a snapshot is missing files, restore another snapshot or fetch the frame again.
- If the snapshot cannot be trusted, check its source URL, hash, mode, and Beam version.
