stone bane
PS C:\windows\system32> openclaw config set discovery.mdns.mode off
🦞 OpenClaw 2026.4.26 (be8c246) — I can't fix your code taste, but I can fix your build and your backlog.
Config overwrite: C:\Users\karle.openclaw\openclaw.json (sha256 8752d645a11603c2f705c233a603ffb8e51c559c9e1f950743b4b31d44b335de -> b2106abb7e93704368c542ca309262910b7b76d27e63e2598677ef85f925b5e5, backup=C:\Users\karle.openclaw\openclaw.json.bak)
Updated discovery.mdns.mode. Restart the gateway to apply.
PS C:\windows\system32> openclaw gateway restart
🦞 OpenClaw 2026.4.26 (be8c246) — Greetings, Professor Falken
Restarted Windows login item: OpenClaw Gateway
PS C:\windows\system32> openclaw gateway status
🦞 OpenClaw 2026.4.26 (be8c246) — More integrations than your therapist's intake form.
|
o
Service: Scheduled Task (registered)
File logs: ~\AppData\Local\Temp\openclaw\openclaw-2026-04-30.log
Command: C:\Program Files\nodejs\node.exe C:\Users\karle\AppData\Roaming\npm\node_modules\openclaw\dist\index.js gateway --port 18789
Service file: ~.openclaw\gateway.cmd
Service env: OPENCLAW_GATEWAY_PORT=18789
Config (cli): ~.openclaw\openclaw.json
Config (service): ~.openclaw\openclaw.json
Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.
Runtime: running (pid 26184, Startup-folder login item installed; listener detected on port 18789.)
Warm-up: launch agents can take a few seconds. Try again shortly.
Connectivity probe: failed
Probe target: ws://127.0.0.1:18789
timeout
Capability: unknown
Port 18789 is already in use.
- pid 26184: node.exe (127.0.0.1:18789)
- Another process is listening on this port.
Listening: 127.0.0.1:18789
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting
PS C:\windows\system32>