DeepSeek Harness Plugin

fish133/dsh-admin-gate

Category Security & Permissions Added 2026-11-15

Password gate in front of the DeepSeek Harness web UI: admins sign in with a password stored only as a scrypt salted hash, and guests enter without one but are held to an allowlist of /api endpoints and agent tools; several admin accounts may exist, each with its own password; three modes (admin-only, guest, open), and closing guest entry drops every guest already inside; conversation ownership is recorded per sessionId so each account sees only its own conversations, with list and search filtering rather than refusing so "exists but you cannot see it" never leaks. The gate is enforced on the host, not in the page: connection.admit, admitConnection and authorizeIndex decide who a visitor is and issue a Peer carrying that identity, connection/request answers 401 or 403, WebSocket streams are checked when they open, tools.guard() keeps guest-triggered agent turns inside the tool allowlist, and the gate page at /admin-gate is mounted outside /api so it does not need the harness cookie. Five failed logins within ten minutes lock the door for five minutes, and state is written to a temporary file and renamed so an interrupted write cannot leave a half-written JSON. The default allowlists deliberately exclude session/prompt and the read, bash and write tools, since those run as the owner. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.

Install

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:fish133/dsh-admin-gate

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.