Beam logoBeam

CLI Command

beam login

Connect Beam to Figma by storing a user-local credential for the Free workflow.

Use this command before beam inspect, beam export, or any MCP tool that needs live Figma access. The MVP login flow uses a Figma personal access token so Beam can prove the local design pipeline without requiring an OAuth app setup.

Credentials are stored in the user Beam directory under the local profile. They are not written into the project, not added to .beam/config.json, and not included in snapshots, debug bundles, package files, or MCP responses.

beam login --token <figma-token> is useful for controlled setup and automation. Interactive beam login is better for normal use because it keeps the token out of shell history when the terminal supports secure input.

beam whoami verifies that Beam can read the local auth state without printing the token value. It should report useful account or credential status while keeping secrets hidden.

bash
1beam login --token <figma-token>2beam login3beam whoami

Run Sequence

  1. Create a Figma personal access token from Figma account settings.
  2. Run beam login --token <figma-token> for scripted setup or beam login for interactive setup.
  3. Run beam whoami to confirm Beam can read the saved credential.
  4. Run beam doctor before inspecting a design.

Expected Output

Beam should confirm that credentials were saved, then beam whoami should report an authenticated local credential without printing the token.

Files And Artifacts

  1. ~/.beam/credentials.json

Next Step

Use beam doctor to validate the full local environment.

Recovery Paths

  1. If the token is rejected, create a new Figma token and confirm the file is shared with that Figma account.
  2. If the credential file cannot be written, check permissions on the user Beam directory.
  3. If a token appears in shell history, rotate it in Figma and log in again interactively.