OpenClaw Setup Not Working

[JMitch0214]

setup-engine-20260609-003711.txt

[clawsweeper]

ClawSweeper status: review started.

I am starting a fresh review of this issue: OpenClaw Setup Not Working This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.

[github-actions]

🤖 This is an automated response from Repo Assist.

Welcome, @JMitch0214! Thanks for filing this issue and attaching the setup log — that's really helpful for diagnosis.

I can see ClawSweeper has already started reviewing. While that review is in progress, a few things that might help the maintainers triage faster:

1. What version are you running? You can find this in the About page of the tray app.
2. What happens exactly? Does the installer fail, the tray app crash on startup, or the setup wizard not complete?
3. Any antivirus / security software? OpenClaw's installer sometimes gets blocked by AV tools — temporarily disabling it during install can help rule that out.

The setup log you attached will be the primary evidence for diagnosis. I've labelled this bug + needs triage so it gets picked up in the next triage pass.

If you can share any additional detail in the meantime, feel free to add it here!

Generated by 🌈 Repo Assist, see workflow run. Learn more.

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@97143ac59cb3a13ef2a77581f929f06719c7402a

[JMitch0214]

v0.6.3

[github-actions]

🤖 This is an automated response from Repo Assist.

Thanks for confirming you're on v0.6.3! That's helpful.

A couple more questions to narrow this down:

1. Which step fails? In the setup wizard, does it get stuck at the "Connecting as operator..." step (pair-operator), or at the "Connecting as node..." step (pair-node)?
2. What error do you see? Does the wizard show "Gateway not reachable" or "Connection refused" or a timeout?

The reason I ask: we've just identified a bug in v0.6.3 where PairOperatorStep was missing a Windows-side gateway connectivity check before attempting the WebSocket connection. WSL port forwarding can lag by a few seconds after the gateway starts, and the missing check caused the connection to fail with a timeout. A fix PR has been submitted.

If you're hitting the pair-operator step specifically, this fix should resolve it. Stay tuned!

Generated by 🌈 Repo Assist, see workflow run. Learn more.

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@97143ac59cb3a13ef2a77581f929f06719c7402a

[github-actions]

This issue has been automatically marked as stale due to inactivity.
Please add updated OpenClaw Windows details or it will be closed.