dsh-lan-access:在 DSH Web 中增加局域网访问开关

`dsh-lan-access` 是一款 DSH Web 插件,旨在简化 DSH 局域网访问的配置管理。DSH 默认仅绑定回环地址(127.0.0.1)以确保安全,拒绝绑定 0.0.0.0。该插件在 `Settings → General` 界面提供“LAN access”开关,允许用户在可信局域网内灵活切换绑定地址:开启时绑定 0.0.0.0,使同网段设备可通过 `http://<LAN-IP>:3080` 访问;关闭时恢复为 127.0.0.1。插件核心功能无需修改 DSH 核心代码,通过注册安全的 JSON 路由实现状态读写与配置同步,并支持远程设置页面访问及浏览器兼容性补丁。安装需执行

Read More
dsh-mobile: Accessing DeepSeek Harness Web GUI on iPhone / iPad

dsh-mobile is an MIT-licensed plugin for DeepSeek Harness (DSH), designed to address the need for accessing the local Harness Web GUI on iOS devices. The plugin launches a LAN reverse proxy (default port 3080) to forward HTTP and WebSocket requests, and injects iOS PWA meta information along with mobile-specific CSS to optimize touch interaction, safe area, and soft keyboard experiences, supporting access similar to a native app via Safari's "Add to Home Screen". Core features include: providing a `/mobile` QR code page for obtaining the access address, supporting configurable IP whitelists to restrict access sources, and a security context patch that fixes the unavailability of `randomUUID` on mobile devices. After installation, it needs to be configured in `cordi

Read More
dsh-remote-link: Securely Expose DSH Web UI to LAN with Agent Session Forking Support

dsh-remote-link is a DSH plugin designed to address the challenge of securely accessing the local DSH Web UI from a mobile phone or LAN device. It authenticates on a dedicated gateway port and reverse-proxies to the loopback address, thereby avoiding security risks associated with directly exposing the Web UI. Key features include: 1. **Secure Remote Access**: Supports one-time QR code pairing, HMAC challenge-response, and HttpOnly Cookie session management, replacing long-term credentials. 2. **Status and Monitoring**: Provides a `/status` page that displays link status, device identity, heartbeat, and upstream health, along with support for host telemetry data subscription. 3. **Model Enhancement**: Introduces a `fork_session` tool, allowing the model to create sub-sessions based on recently completed rounds, facilitating exploratory...

Read More
dsh-lan-access: Enabling Access to the DSH Web GUI Within the Local Area Network

dsh-lan-access is a DSH network access tool plugin maintained by Leon0555 (MIT, v0.1.3). It binds the Web GUI to 0.0.0.0, injects a crypto.randomUUID polyfill to fix RPC failures over HTTP in LAN, and supports narrow-screen mobile layout since v0.1.2. One-click npm installation: dsh plugin --profile web add dsh-lan-access. Restricted to trusted internal networks: no authentication, and the configuration/credential interfaces remain accessible only via localhost loopback.

Read More
dsh-web-lan-access: Enable DSH Web UI for LAN HTTP Access

dsh-web-lan-access is a DSH Web plugin maintained by AcidGr, designed to resolve the issue where crypto.randomUUID is unavailable when accessing via plaintext HTTP on non-loopback addresses, which prevents sessions and models from loading. The plugin injects a polyfill through webServer.tapIndex, automatically binds the webserver to 0.0.0.0, and extends the /api trust fence to cover LAN and Tailscale IPs. Installation is performed with the command `dsh plugin --profile web add dsh-web-lan-access`, and once started, remote access is available via http://<server-ip>:3080. Note the security risks of exposing 0.0.0.0, as well as the known limitation that certain APIs, such as settings/credentials, remain restricted to loopback only.

Read More
Make DeepSeek Harness Web UI support LAN access via dsh-web-lan-access

DeepSeek Harness Web UI works normally only on localhost by default. When accessing via pure HTTP in a local area network, the front end will fail to render sessions and models due to the lack of `crypto.randomUUID` in a secure context. The community plugin *dsh-web-lan-access* (maintained by AcidGr, MIT licensed, npm version 1.1.0) injects polyfills through the official `index-tap` and binds the webserver to `0.0.0.0`. This article organizes installation commands, LAN/Tailscale usage methods, verification steps, and precautions such as unauthenticated exposure and the settings page only being accessible via loopback, based on the directory page and GitHub documentation.

Read More