CLI Command
beam export
Write local visual references, exportable assets, and the canonical asset manifest.
beam export is for local ground truth. It should write rendered frame references, exportable image or vector assets, and a manifest that follows Beam's canonical Asset Manifest Contract.
Exports use the same core pipeline as inspect. The CLI should not duplicate Figma fetching, cache access, snapshot behavior, or asset discovery logic outside Beam Core.
Output paths are local project files. Beam Free should not upload assets, sync customer data, or require a hosted account to complete the export.
--json should return stable paths and warnings so agents or scripts can use the exported files without scraping terminal text.
1beam export <figma-url>2beam export <figma-url> --out .beam/assets3beam export <figma-url> --json
Run Sequence
- Run
beam inspect <figma-url>first if you want to review the frame and evidence state. - Run
beam export <figma-url>to write the rendered reference and exportable assets. - Open the asset manifest to see every exported node, output path, format, and scale.
- Point the coding agent at the exported files when implementing image-heavy screens.
Expected Output
Beam should report the snapshot id, exported frame image path, asset count, manifest path, skipped nodes, and warnings for assets that could not be exported.
Files And Artifacts
- .beam/cache/images/<snapshot-id>.png
- .beam/cache/assets/<asset-name>.<format>
- .beam/cache/assets/<snapshot-id>.manifest.json
Next Step
Use the manifest paths in the implementation and compare the local page afterwards.
Recovery Paths
- If no assets export, confirm the selected frame actually contains exportable images, vectors, or fills.
- If an asset is missing, provide the source file manually or ask Beam for a node image.
- If output paths are unexpected, pass
--out <directory>explicitly.
