CLI Command
beam debug bundle
Create a sanitized local support bundle for fetch, cache, simplify, and MCP issues.
beam debug bundle is for support and investigation. It should collect useful local diagnostics such as config without secrets, recent logs, snapshot metadata, MCP config state, environment information, and command outcomes.
Credentials are excluded by default. Tokens must not appear in bundle files, terminal output, logs, errors, or MCP responses.
Raw Figma payloads are customer data. They require explicit opt-in through --include-raw, and the command should make that choice visible before producing a bundle.
The bundle helps determine whether an issue came from Figma access, Beam fetching, cache state, simplification, asset export, MCP transport, or visual comparison.
1beam debug bundle2beam debug bundle --out .beam/debug3beam debug bundle --include-raw
Run Sequence
- Run
beam doctorfirst so the obvious setup state is captured separately. - Run
beam debug bundleto create a redacted support bundle. - Inspect the bundle summary before sharing it.
- Use
--include-rawonly when raw Figma payloads are required for debugging.
Expected Output
Beam should print the bundle path, included diagnostic categories, redaction status, and any files that were intentionally skipped.
Files And Artifacts
- .beam/debug/<timestamp>/summary.json
- .beam/debug/<timestamp>/logs/
- .beam/debug/<timestamp>/snapshots/
Next Step
Use the bundle to isolate whether the issue is auth, Figma access, cache, simplification, MCP, or compare.
Recovery Paths
- If the bundle includes sensitive design data, delete it and rerun without
--include-raw. - If logs are missing, reproduce the failing command and create the bundle again.
- If the bundle cannot be written, pass
--out <directory>to a writable location.
