-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
[Bug]: Editing WebSocket URL clears Gateway Token in Overview #41545
Copy link
Copy link
Closed
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.bugSomething isn't workingSomething isn't workingbug:behaviorIncorrect behavior without a crashIncorrect behavior without a crashclawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.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.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.Auth, provider routing, model choice, or SecretRef resolution may break.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.staleMarked as stale due to inactivityMarked as stale due to inactivity
Description
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.bugSomething isn't workingSomething isn't workingbug:behaviorIncorrect behavior without a crashIncorrect behavior without a crashclawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.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.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.Auth, provider routing, model choice, or SecretRef resolution may break.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.staleMarked as stale due to inactivityMarked as stale due to inactivity
Type
Fields
Priority
None yet
Bug type
Behavior bug (incorrect output/state without crash)
Summary
Editing the WebSocket URL in Overview → Gateway Access clears the Gateway Token field immediately. This causes Connect to fail unless the token is entered again.
Steps to reproduce
Expected behavior
Editing the WebSocket URL should not clear the Gateway Token field. The token should remain unchanged unless the user explicitly edits or clears it.
Actual behavior
As soon as the WebSocket URL field is edited, the Gateway Token field is cleared immediately.
If the user then clicks Connect without re-entering the token, the connection fails.
OpenClaw version
2026.3.8 (source checkout from upstream/main, reproduced at commit c9a6c54)
Operating system
Windows 10
Install method
pnpm ui:devon Windows 10Logs, screenshots, and evidence
The issue is reproducible with frontend only. I was able to reproduce it without the backend running: - enter a token in Gateway Token - edit WebSocket URL - token is cleared immediately before focus leaves the URL inputImpact and severity
This issue is consistently reproducible and causes connection attempts to fail unless the user notices that the token was cleared and re-enters it manually.
Additional information
This appears to be a frontend-only bug. I reproduced it on the latest upstream/main and verified:
It seems related to the WebSocket URL input handling in
ui/src/ui/views/overview.ts, where editing the URL may be resetting the stored token value during input.