AI Agent Hub
Back to plugins
🧩

dsh-lan-link

admin-security Updated 2026.09.16

Run the following command in DeepSeek Harness:

dsh plugin install advance-lion/dsh-lan-link

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install advance-lion/dsh-lan-link in the DeepSeek Harness CLI to install this plugin; source code at https://github.com/advance-lion/dsh-lan-link .

About this plugin

DeepSeek Harness Web binds to 127.0.0.1 by default, so a second laptop or tablet on the same network has no way to open the console without SSH tunneling or manually typing --host flags every single time. dsh-lan-link turns that into a single toggle in the settings panel: enable LAN access, pick a port, set the cookie lifetime, save, and restart. The plugin does not ship a second reverse-proxy layer or a bespoke auth scheme — it simply configures and exposes the LAN binding, trustedHosts fence, per-process random launch token, and signed HttpOnly cookie that DSH 0.1.5 already provides out of the box.

Every security concern stays native. The cookie is HttpOnly, SameSite=Strict, host-only, and bound to the exact hostname and port; changing any of those invalidates the session instantly. Host, Origin, and sec-fetch-site checks are enforced by DSH's own trust fence. The full token URL is equivalent to complete operator access, and the settings card surfaces plain-language reminders: do not publish the port to the public internet, avoid public Wi-Fi, and restrict Windows Firewall to private networks only. Revoking a single browser is as simple as clearing its cookie; revoking every browser means deleting or replacing the credential file and restarting DSH.

This plugin is aimed at developers who work across two or three machines on a home or small-office LAN and want persistent, zero-copy-paste access to DSH Web. No custom Nginx config, no hand-typed --host flags after every restart, no middleware to maintain — one checkbox, one restart, and a clean URL that keeps working across DSH restarts until the cookie expires or you clear it.

Use Cases

  • Open the DSH Web console from a tablet or second laptop on the same LAN
  • Keep browser authorization across DSH restarts without re-copying the token URL
  • Provide a persistent access entry for collaborators on a home or small-office network

Best For

  • Solo developers who use DSH Web from multiple machines
  • Developer teams in home or small-office setups that share DSH over LAN
  • Lightweight operators who prefer no Nginx config or hand-typed --host flags