cross-host-rig-commands

1# Cross-host rig commands
2 
3Use a registered host address and the entry's declared transport. SSH entries
4run a remote CLI through a single-hop shell; HTTP entries use the remote daemon.
5These paths have different prerequisites and command coverage. Check the exact
6command's help and the target installation before a consequential operation.
7 
8## Choose and inspect the destination
9 
10`rig host list` shows registered hosts. `rig host add --help` describes registry
11writes; `rig host doctor --help` describes reachability checks. Inspect the
12configured OpenRig home rather than assuming the default `~/.openrig/hosts.yaml`.
13Registry changes affect later routing, so make them within the requested scope.
14 
15```yaml
16hosts:
17  - id: test-vm
18    transport: ssh
19    target: test-vm.local
20    user: example-user
21  - id: remote-dev
22    transport: http
23    url: http://remote-dev.example:7433
24    bearer_env: REMOTE_RIG_TOKEN
25```
26 
27The registry requires a hosts array, unique non-empty ids and a supported
28transport. SSH needs a non-empty target; user and notes are optional. HTTP needs
29a URL and accepts at most one of bearer_env or bearer_file. Omitting both is
30valid for a tokenless target. A configured but unavailable bearer is a permission
31failure, not anonymous fallback. Host ids also have reserved-name validation;
32use the actual validator's error rather than inventing an alias that collides.
33 
34## Address the intended operation
35 
36```bash
37…