sudo robotctl net connect

sudo robotctl net connect <ssid> --psk <passphrase>
sudo robotctl net connect <ssid> --psk-stdin

Joins the robot to a wireless network. Omit --psk for an open one.

--psk-stdin reads the passphrase from standard input, keeping it out of your shell history.

Two behaviours to expect

Joining disconnects the robot from the network it is on. So an ssh session over wifi drops — that is the command working, not failing.

It can take a while to answer. The figure the official docs give on the duckctl side is up to 45 seconds.

The chicken and the egg

If the robot has never joined a network, you cannot ssh in to run this. That case goes over Bluetooth: duckctl wifi connect needs no network of its own.

net.connect is refused over WebRTC by design, precisely because configuring the network must have a path that does not depend on the network.