Skip to content

OpenClaw README: Connect works from a local Control UI only - #44

Merged
chenchenSimular merged 1 commit into
mainfrom
openclaw-readme-https
Nov 9, 2026
Merged

chenchenSimular merged 1 commit into
mainfrom
openclaw-readme-https

Conversation

@dora-dotcom

Copy link
Copy Markdown
Collaborator

The README said Connect works from the Control UI on the Gateway's HTTPS or Tailscale address. With the client document (0.1.1), it doesn't: the callback is the address the browser used, and /oauth/openclaw.json on box.simular.ai can list only loopback callbacks (box-portal #291). box refuses any other address. The README now says so and points those users to the CLI sign-in.

Tested 9 Nov: 0.1.1 from main, OpenClaw 2026.11.1, Control UI on 127.0.0.1:18789. Connect showed the verified consent page ("From box.simular.ai"), and after Allow the plugin page showed Connected. 0.1.1 has been submitted to ClawHub. This README change goes out with the next release.

🤖 Generated with Claude Code

box refuses an HTTPS or Tailscale dashboard address: the client document on
box.simular.ai can list only loopback callbacks (box-portal #291).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chenchenSimular
chenchenSimular merged commit 995b9b0 into main Nov 9, 2026
27 checks passed
@chenchenSimular
chenchenSimular deleted the openclaw-readme-https branch November 9, 2026 11:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants