Skip to main content
The CLI supports account setup, diagnostics, live capacity checks, session cleanup, a curated simulator, and the turnkey SO-101 path.
Use dropbear <command> --help as the exact installed-version reference.

​
Account and health

Credentials are written to ~/.dropbear/config.toml. Never print or commit that file.

​
Capacity

status checks live model-region capacity without opening a cloud session. Current model access and account-specific availability also appear in the dashboard.

​
Sessions

Use --all only when you intend to terminate every open session on the account. Closing sessions stops continued usage from abandoned leases.

​
Local simulation

The sim command runs Dropbear’s curated local LIBERO path on your machine. It is not a generic adapter for your own simulator, and Dropbear does not host a browser-based simulator:
Useful options:
  • --task-suite and --task-id select a LIBERO task.
  • --task-seed sets the initial-state seed.
  • --max-steps or --max-duration sets one episode budget.
  • --non-interactive disables the viewer and prints a JSON summary.
  • --transport auto|quic|relay selects the network path.
  • --region nearest|available|<AWS region> selects placement.
  • --verbose exposes raw session and endpoint diagnostics.
  • --output-root <path> writes a run artifact bundle.
The sim extra is Linux/WSL2 only. Run dropbear doctor sim first.

​
SO-101

  • setup detects and saves the arm, side camera, and wrist camera.
  • calibrate writes ~/.dropbear/calibration/so101.json.
  • doctor so101 gates the hardware path.
  • run pick-place starts dry on a newly configured machine and asks for explicit confirmation before persisting motion.
  • --no-fallback refuses the hosted relay if QUIC/UDP is unavailable.
Read the complete SO-101 safety sequence before running the motion command.

​
Shell completion

If a documented command is missing, compare dropbear --help with 0.1.0a9 and follow the upgrade instructions.