2539bcafe0
The dashboard WebSocket client was only sending ['zeroclaw.v1'] as the protocols parameter, omitting the bearer token subprotocol. When require_pairing = true, the server extracts the token from Sec-WebSocket-Protocol as a fallback (browsers cannot set custom headers on WebSocket connections). Without the bearer.<token> entry in the protocols array, subprotocol-based authentication always failed. Include `bearer.<token>` in the protocols array when a token is available, matching the server's extract_ws_token() expectation. Closes #3011 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| api.ts | ||
| auth.ts | ||
| i18n.ts | ||
| sse.ts | ||
| uuid.ts | ||
| ws.ts | ||