You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The stupid nullhub.local / nullhub.localhost binding seems to be the issue.
It won't even work with nullhub-windows-x86_64.exe serve --host 127.0.0.1
It does however work with your LAN IP, like nullhub-windows-x86_64.exe serve --host 192.168.0.222
Splitting this into the two things it mixes together:
1. The empty ui/ folder is expected — the dashboard you see at http://127.0.0.1:19800 is embedded in the nullhub binary itself (that includes v2026.4.17), so an empty ui/ folder doesn't block it. That folder holds installable UI modules (like the chat UI for managed NullClaw instances), not the dashboard.
2. The page not opening in your browser is the host binding issue @Luckz identified: on your Windows setup the default hosts don't resolve. Workaround: nullhub-windows-x86_64.exe serve --host <your-LAN-IP> (e.g. 192.168.0.222) and open that.
3. Re: "is there another web ui to be installed" — yes, the chat UI module for managed instances. On current releases it needed a one-time manual install (nullhub#20 has the details, along with the fixed nullclaw-chat-ui v2026.9.28 release); #84 makes it automatic on startup for any hub with a NullClaw instance.
If the --host workaround doesn't get the dashboard loading for you, comment back and we can open a dedicated issue for the Windows binding problem.
Activity
kubikanber commentedon Apr 24, 2026
When we run it, it creates the .nullhub folder. But the ui folder is empty. Is this why the web interface isn't working?
Or is there something I'm missing? Please help.
Luckz commentedon Sep 16, 2026
The stupid nullhub.local / nullhub.localhost binding seems to be the issue.
It won't even work with
nullhub-windows-x86_64.exe serve --host 127.0.0.1It does however work with your LAN IP, like
nullhub-windows-x86_64.exe serve --host 192.168.0.222vernonstinebaker commentedon Sep 28, 2026
Splitting this into the two things it mixes together:
1. The empty
ui/folder is expected — the dashboard you see athttp://127.0.0.1:19800is embedded in the nullhub binary itself (that includes v2026.4.17), so an emptyui/folder doesn't block it. That folder holds installable UI modules (like the chat UI for managed NullClaw instances), not the dashboard.2. The page not opening in your browser is the host binding issue @Luckz identified: on your Windows setup the default hosts don't resolve. Workaround:
nullhub-windows-x86_64.exe serve --host <your-LAN-IP>(e.g.192.168.0.222) and open that.3. Re: "is there another web ui to be installed" — yes, the chat UI module for managed instances. On current releases it needed a one-time manual install (nullhub#20 has the details, along with the fixed nullclaw-chat-ui v2026.9.28 release); #84 makes it automatic on startup for any hub with a NullClaw instance.
If the
--hostworkaround doesn't get the dashboard loading for you, comment back and we can open a dedicated issue for the Windows binding problem.