Monitor nodes require manual page refresh to appear (WebSocket not streaming live)

[kit-the-fox]

Description

Activity nodes don't appear in real-time on the monitor. Users need to manually refresh the page to see new nodes after agent actions.

Expected Behavior

Nodes should appear automatically as activity streams in via WebSocket, without needing page refresh.

Actual Behavior

• Agent performs actions (exec, API calls, etc.)
• Monitor page shows nothing new
• After manual page refresh, the node appears
• Node disappears again on next refresh

Environment

• Crabwalk v1.0.9
• Windows 10
• OpenClaw gateway on ws://127.0.0.1:18789
• Browser: Edge (also tested via network IP on mobile)

Steps to Reproduce

1. Start crabwalk daemon
2. Open /monitor in browser
3. Have agent perform an action
4. Observe: no node appears
5. Refresh page
6. Node now visible (briefly)

Seems like the WebSocket connection might not be properly streaming events to the frontend.

[Popidge]

Could also relate to #43 and #44 - error handling and UI feedback on gateway connection issues. Although the "refresh shows nodes" means it's a separate issue, possibly something in the websocket poll -> tRPC -> render pipeline?

[Popidge]

Will be worth checking if PR #46 improves this, as it focuses on platform compatibility for Windows as well.

[luccast]

Yea, hard to know what this relates to. Needs to be replicated before we work on it, just keep an eye on it.