Summary

Two related problems with the port forward created during nemoclaw onboard:

1. Binds to 127.0.0.1 — remote clients (other machines on the network)
   cannot reach the dashboard even when CHAT_UI_URL is set to a remote host.
2. Not restored after sandbox recreate — if the sandbox is deleted and
   re-onboarded, the port forward is gone and must be manually restarted.

Problem 1: 127.0.0.1 default

nemoclaw onboard starts the port forward via openshell forward start, which
binds to 127.0.0.1:18789 by default. When CHAT_UI_URL is set to a remote
hostname for network access, the dashboard is unreachable because the forward
only accepts connections from localhost.

Workaround:

openshell forward stop 18789 <sandbox-name>
openshell forward start --background 0.0.0.0:18789 <sandbox-name>

Expected behavior: When CHAT_UI_URL is set to a non-localhost address,
onboarding should bind the forward to 0.0.0.0 automatically.

Problem 2: Forward not restored after recreate

After nemoclaw onboard is re-run (e.g. to pick up config changes), the port
forward is not re-established. The dashboard becomes unreachable with no
indication of why — the sandbox is running but nothing is forwarding to it.

Expected behavior: nemoclaw onboard should restore any port forwards it
previously created, or document that this is a required manual step.

Environment

• NemoClaw v0.1.0
• OpenShell v0.0.14