dsh-auth-gate

DeepSeek Harness assumes a local, loopback-only client, and its trust fence is nothing more than a browser CSRF guard that validates Host, Origin, and Sec-Fetch-Site headers. The moment you put it behind Docker, an Nginx or Caddy reverse proxy, a cloud VM, or share it across a team, that fence stops protecting anything—anyone who can reach the port gets full Agent control. dsh-auth-gate closes that gap by layering real authentication onto every existing and future HTTP and WebSocket route: Bearer Token for scripts, a session login page with HttpOnly and SameSite=Strict cookies for browsers, and a per-session waterfall rate limiter for approval prompts. When the internal route registry changes, the plugin fails closed rather than silently letting unauthenticated traffic through. Credentials live in environment variables and are never written into a patch file; every restart rotates the session secret so stale browser sessions die instantly, and login attempts are throttled to five per source address per minute. Designed for developers running Harness in containers, behind reverse proxies, or on CI runners, and for teams that need token-based API access alongside a human login page, it turns an otherwise naked control plane into an authenticated, rate-limited, and revocable service. It does not provide per-user sandboxing or audit logging, but as the first gate in a defense-in-depth chain it ensures that reaching the port is no longer the same as owning the Agent.