Files
Codeman/.changeset/dsh-web-launch-token.md
T
ArizeSky 238853f96a fix(webview): keep dashboard cookies alongside the injected one
The managed DeepSeek tab is trusted, so the browser's own cookies for the
dashboard are forwarded. The injected dsh credential replaced that header
instead of joining it, dropping any other cookie dsh had set. Append the
pair to the filtered browser cookies and leave the rest untouched.
2026-11-16 16:10:51 +08:00

1.2 KiB

aicodeman
aicodeman
patch

The DeepSeek Harness web tab opens on the dashboard again instead of a blank 401 page. dsh web now gates its own index behind a one-time launch token it prints on boot; the supervisor reads that token out of the captured output, trades it for the session cookie once at startup, and the webview proxy presents the cookie on both the HTTP and WebSocket legs — scoped to the loopback authority it was minted for. It is appended to the dashboard's own cookies rather than replacing them. The banner reader scans every dsh web: line (diagnostics share the prefix) and only complete lines (a split write is waited for), so a dsh web: loading profiles line no longer makes boot give up. The printed token URL is only fetched when it names 127.0.0.1 on the port that was just spawned. A server whose exchange failed is no longer reused, so asking to start the UI again restarts it and retries the exchange. The cookie is only presented to a tab whose owner holds the privileged-commands grant, and in multi-user mode only to the owner whose request started the process: managed is a client-supplied field and the live port is public, so the saved record alone is not an entitlement. A dsh without the gate keeps working unchanged.