CLI

strands-robots wraps the same functions the agent tools call.

command	does
list	robots and policies in the registry
observe <robot> [--mode sim\|real\|twin] [--port P]	one observation as JSON
move <robot> '<json>' [--mode ...] [--dry-run] [--confirm]	one action; real needs --confirm
run <robot> --policy P --instruction T [--steps N] [--hz HZ] [--record USER/NAME]	a policy rollout with RTC
record <robot> <user/name> --policy P --instruction T [--steps N] [--fps F]	one episode into ~/.strands_robots/datasets/<user/name> (lerobot format; the directory must not exist)
teleop <follower> --leader L --leader-port P [--steps N] [--record USER/NAME]	a real leader arm drives the follower; add --confirm for a real follower
serve <robot> [--peer-id ID] [--mhs BROKER]	one mesh peer for this robot, and an MHS device with --mhs
mhs fleet mhs invoke <device> <procedure> '<json>' [--broker B]	an MHS fleet from the shell
dashboard [--host H] [--dashboard-port 8080]	the operator console
doctor	which extras are installed, and every knob
acceptance	bash acceptance/all.sh
info <path>	dataset info for the directory record returned

strands-robots doctor
strands-robots observe so101 --mode sim
strands-robots move so101 '{"shoulder_pan": 0.3}' --mode sim
strands-robots run so101 --policy mock --instruction "wave" --steps 30
strands-robots record so101 me/wave --policy mock --instruction "wave" --steps 30
strands-robots info ~/.strands_robots/datasets/me/wave

Every command defaults to --mode sim; real motion refuses with CONFIRM_REQUIRED without --confirm. Output is the same envelope the agent tools return: {"ok": true, "result": ...} or {"ok": false, "refusal": {"code", "value", "cause", "remedy"}}.