jupyter-dsh-proxy

A jupyter-server-proxy launcher entry for the DeepSeek Harness (dsh) web UI.

It adds a "DeepSeek Harness" tile to the JupyterLab launcher that opens the dsh web UI in a new tab — without requiring code-server / VS Code to be running first.

How it works

The dsh web server is started independently at pod boot by the 41-dsh-web boot hook (in the divenb image), which runs dsh web on a fixed loopback port. This package registers a PORT-mode proxy spec that points at that already-running server:

browser → jupyter-server-proxy (/dsh/) → dsh web (127.0.0.1:<port>)

The spec uses {"port": <P>, ...} — not url mode. jupyter-server-proxy 4.x's ServerProcess has no url traitlet; a url-only spec registers no proxy handler and the tile 404s. Port mode registers a real _Proxy handler at the tile's link path (/…/dsh/). request_headers_override pins the Host header to the loopback bind (mirrors jupyter-hermes-proxy).

The same dsh web instance is shared with the VS Code extension: the extension only auto-starts dsh web when nothing is already listening at its dsh.url, so a boot-hook-owned instance is used by both entry points.

Port selection

The launcher resolves the target port in this order:

1. ~/.dsh/web.port — written by the 41-dsh-web boot hook (single source of truth for a non-default port).
2. DSH_WEB_PORT env var — a literal number, or random / auto / 0 to pick a free port (used only if web.port is absent).
3. default 3080 — the dsh web default and the VS Code extension default, so both entry points agree with no configuration.

The port is a documented dsh web flag (dsh web --port <P>), not a patched default, so it survives dsh version bumps.

Installation

uv pip install /path/to/jupyter-dsh-proxy

The dsh entry point is auto-discovered by jupyter-server-proxy; no additional configuration is required. The launcher tile appears under the "Other" section.