wendy vm robot configure
Attach a robot profile to an existing VM
Syntax
wendy vm robot configure <name> [flags]Examples
wendy vm robot configure --helpArguments
Argument notation from the CLI: <name>. Angle brackets mark required values; square brackets mark optional values. See Details for command-specific validation.
Flags
Flags below include inherited options. Types and defaults come from the CLI source. An empty default means no value is configured.
| Flag | Type | Default | Description |
|---|---|---|---|
--device | string | (empty) | Target device host (hostname, IP, or host:port); 'wendy run' accepts a comma-separated list to deploy one build to several devices (needs a remote build host and --detach). Defaults to $WENDY_DEVICE, then the saved default device |
--json | bool | false | Output in JSON format |
--profile | string | go2 | Robot profile: go2, g1, so101 or rosmaster-r2 |
--yes / -y | bool | false | Accept prompts, including installing QEMU when it is missing (Linux still asks before running sudo) |
Output
Output depends on the operation and selected target. Command behavior and detailed examples.
JSON output
The global --json option requests machine-readable output. The CLI also selects JSON mode when no interactive terminal is attached. Support and payloads are command-specific; this flag does not guarantee a single JSON document for commands that stream logs or invoke build tools. Consult Details before parsing command output.
Exit codes
The CLI entry point returns 0 on success and for its user-cancelled or default-cleared results. Other returned errors exit with 1 and print a diagnostic to stderr. Some operations may terminate through subprocess or signal handling; do not infer application health from the CLI exit code alone.
Common errors
Check argument values and flag combinations against the synopsis above. For discovery, build, port, and readiness failures, see deployment troubleshooting. Command-specific constraints are in Details.
See also
Details
Attach a Go2, G1, SO-101 or ROSMASTER R2 profile to an existing VM, pinning this CLI's robot runtime. Existing robot profiles are never replaced.
This records the profile without booting or restarting the VM. Run 'wendy vm robot start <name>' to build and start the robot runtime.