Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Companion hangs after connecting to remote Gateway (node bootstrap_token_invalid loop, then freeze loading large chat history); Settings unreachable

Open
  • Is something wrong?
#1,714 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
22/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
authentication, desktop-dev

Research direction

The report covers several separate failures: a node-mode bootstrap_token_invalid reconnect loop, a UI-thread freeze while loading a large chat history, a FORBIDDEN users.self call that blocks startup, and a Settings menu that stays unresponsive. Start by reproducing with nodeMode=true and reading the node connection code and the startup path that calls users.self. Keep the scope to one of these failures, since the reporter's expected outcomes are separate fixes.

Written by the indexing model from the issue text.

Description

clawsweeper:needs-info clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr impact:auth-provider impact:crash-loop impact:ux-release-blocker issue-rating: 🦐 gold shrimp P0

Summary

OpenClaw Companion (Windows Hub) becomes unresponsive ("not responding") right after connecting to a remote Gateway, and stays that way across restarts. While it is hung, tray menu items such as Companion Settings… do nothing, so node mode cannot be configured or repaired from the UI.

Environment

  • Windows Hub: 2026.9.8-1 (x64, Windows 11)
  • Gateway: 2026.9.7 on macOS, protocol 4, auth mode token
  • Connection: remote Gateway over Tailscale Serve (wss://<host>.ts.net, tailnet-only, valid Let's Encrypt cert), paired with a setup code from openclaw qr --setup-code-only --url wss://…
  • Setup choices: Advanced → existing Gateway, capabilities preset Balanced, model "Current model"

Timeline (from %LOCALAPPDATA%\OpenClawTray\Logs\diagnostics.jsonl + Gateway log)

  1. 12:26 app.start nodeMode=false → Connected, healthy. Operator device pairing approved on the Gateway (openclaw devices approve). Setup wizard completes ("Your AI is ready").
  2. 12:39 app.start nodeMode=true (turned on by the Balanced preset). Node client Windows Node (BSH-OFFICE) node v2026.9.8-1 role=node auth=bootstrap-token is rejected by the Gateway every reconnect: reason=bootstrap_token_invalid (the setup code had already been redeemed by the operator connection). App becomes "not responding".
  3. User ends the task and reopens: still hung.
  4. nodeMode set to false by hand in %APPDATA%\OpenClawTray\settings.json, app reopened at 13:07: the node retries stop, and the operator connection succeeds (health, agents.list, node.list OK). chat.history returns in about 1.35 s for a very large, long-running main session (months of messages and tool output). Two users.self calls fail with FORBIDDEN … requires an authenticated user on every connect. The UI is still frozen, and Companion Settings does nothing.

Expected

  • The app stays responsive when node bootstrap auth fails. It should show a pairing or repair prompt instead of hanging.
  • The setup wizard should not reuse an already-redeemed setup code for node mode. Either mint or request a node credential, or tell the user a second code is needed.
  • Loading a very large chat history should not block the UI thread. Paginate, or lazy-load the history.
  • A failing users.self (FORBIDDEN) should not block startup.

Workaround in use

The browser Control UI works over the same Tailscale Serve URL. Node mode is not usable.

Happy to provide more logs, or test a build.

Dominant language
C#
Stars
2.1k
Forks
315
Avg merge
2d 1h
Merged PRs (30d)
127

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openclaw/openclaw-windows-node

All issues in openclaw/openclaw-windows-node

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.