-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
[[Bug]: Windows Companion gives "Auth did not match" and openclaw onboard redirects to MyClaw.ai #100075
Copy link
Copy link
Closed as not planned
Closed as not planned
Copy link
Labels
P0Emergency: data loss, security bypass, crash loop, or unusable core runtime.Emergency: data loss, security bypass, crash loop, or unusable core runtime.bugSomething isn't workingSomething isn't workingclawsweeper:needs-infoClawSweeper needs more reporter information before it can verify this issue.ClawSweeper needs more reporter information before it can verify this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.Auth, provider routing, model choice, or SecretRef resolution may break.impact:ux-release-blockerA non-technical user is blocked without terminal, logs, config, or support.A non-technical user is blocked without terminal, logs, config, or support.issue-rating: 🦪 silver shellfishThin issue quality; more reproduction proof or environment detail is needed.Thin issue quality; more reproduction proof or environment detail is needed.regressionBehavior that previously worked and now failsBehavior that previously worked and now failsstaleMarked as stale due to inactivityMarked as stale due to inactivity
Description
Metadata
Metadata
Assignees
Labels
P0Emergency: data loss, security bypass, crash loop, or unusable core runtime.Emergency: data loss, security bypass, crash loop, or unusable core runtime.bugSomething isn't workingSomething isn't workingclawsweeper:needs-infoClawSweeper needs more reporter information before it can verify this issue.ClawSweeper needs more reporter information before it can verify this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.Auth, provider routing, model choice, or SecretRef resolution may break.impact:ux-release-blockerA non-technical user is blocked without terminal, logs, config, or support.A non-technical user is blocked without terminal, logs, config, or support.issue-rating: 🦪 silver shellfishThin issue quality; more reproduction proof or environment detail is needed.Thin issue quality; more reproduction proof or environment detail is needed.regressionBehavior that previously worked and now failsBehavior that previously worked and now failsstaleMarked as stale due to inactivityMarked as stale due to inactivity
Type
Fields
Priority
None yet
Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
The local Windows Companion reports an "Auth did not match" error, and running 'openclaw onboard' redirects the browser to the hosted MyClaw.ai subscription page instead of opening a local chat interface.
Steps to reproduce
Expected behavior
The Windows Companion should successfully authenticate with the local Gateway, and 'openclaw onboard' should open a local user interface or chat session without forcing a hosted cloud subscription.
Actual behavior
The Dashboard explicitly displays "Auth did not match", and the onboarding command forces a redirect to the MyClaw.ai landing page prompting for a subscription.
OpenClaw version
NOT_ENOUGH_INFO
Operating system
Windows
Install method
CLI / Windows Companion
Model
Gemini Pro
Provider / routing chain
Google Gemini API
Additional provider/model setup details
No response
Logs
Screenshots, recordings, and evidence
No response
Impact and severity
Additional information
User is trying to determine if a paid MyClaw.ai subscription is now an absolute requirement to use the local interface/Windows Companion, or if the "Auth did not match" error is an independent configuration bug.