Summary
Currently, running waku-daemon on a remote server, VPS, or dedicated workstation (e.g. Mac mini / Linux server over Tailscale/LAN) is a fantastic workflow—heavy build tasks, Docker/git worktrees, and ACP/model processes run on the host while the client remains lightweight.
While apps/mobile already features a dedicated GUI daemon manager (daemons.tsx / daemon-editor.tsx) to configure WebSocket endpoints and auth tokens, the Desktop client currently relies on environment variables (WAKU_DAEMON_ADDRESS and WAKU_DAEMON_TOKEN). On macOS, setting these for GUI bundles requires launching via terminal or creating a LaunchAgent (launchctl setenv / plist).
Proposal
- Desktop Daemon Profile Manager: Add a "Remote Daemons" section in Desktop Settings (or a daemon switcher in the sidebar/window chrome) matching the mobile app's profile manager, allowing users to enter a daemon address (
ws:// / wss://) and token directly.
- Documentation: In the interim, document how to connect Desktop to a remote daemon host in the root
README.md.
Summary
Currently, running
waku-daemonon a remote server, VPS, or dedicated workstation (e.g. Mac mini / Linux server over Tailscale/LAN) is a fantastic workflow—heavy build tasks, Docker/git worktrees, and ACP/model processes run on the host while the client remains lightweight.While
apps/mobilealready features a dedicated GUI daemon manager (daemons.tsx/daemon-editor.tsx) to configure WebSocket endpoints and auth tokens, the Desktop client currently relies on environment variables (WAKU_DAEMON_ADDRESSandWAKU_DAEMON_TOKEN). On macOS, setting these for GUI bundles requires launching via terminal or creating a LaunchAgent (launchctl setenv/plist).Proposal
ws:///wss://) and token directly.README.md.