picoclaw/web/frontend/src/features/chat
Guoguo 6a8552a664
fix(web): derive WebSocket URL from browser location instead of backend (#2405)
The frontend previously used ws_url returned by /api/pico/token, which
is built from the launcher's own port. Behind a reverse proxy this can
produce incorrect URLs (e.g. ws://localhost:18800 instead of the
proxy's public address).

Since the launcher already proxies /pico/ws on the same port, the
frontend can simply use window.location.host to construct the
WebSocket URL, which is always correct regardless of proxy layers.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-07 17:37:01 +08:00
..
controller.ts fix(web): derive WebSocket URL from browser location instead of backend (#2405) 2026-04-07 17:37:01 +08:00
history.ts feat(web): support image messages in pico chat (#2299) 2026-04-03 14:15:20 +08:00
protocol.ts feat(web): support image messages in pico chat (#2299) 2026-04-03 14:15:20 +08:00
state.ts fix(web): refactor pico chat flow and fix proxied websocket URLs (#1639) 2026-03-16 16:25:16 +08:00
websocket.ts feat(web): protect launcher dashboard with token and SPA login (#1953) 2026-03-29 13:11:43 +08:00