@uumit-ai/dsh-uumit-remote
DeepSeek Harness 插件：通过 UUMit 在手机或任何计算机上打开您的 DSH，支持配对、访问控制和邀请。无需桌面客户端。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:uumit-ai/dsh-uumit-remote#9e64809f6db492f5eff4381cb90ddbbb7164c215
Uumit Remote 以 @uumit-ai/dsh-uumit-remote 发布，当前版本为 0.1.0-beta.3。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 简体中文
A DeepSeek Harness (DSH) plugin that lets you open the DSH running on your computer from your phone or any other computer, through UUMit. No desktop client to install.
After installing, click Remote access (远程访问) next to the settings button at the bottom of the DSH sidebar. A panel opens inside DSH where you connect to UUMit and choose who can use it. You, and the people you invite, then open the app URL (like https://dsh--<your-computer>.<UUMit address domain>/) and get the same DSH as on your computer: chats, terminal, files and settings all work, and settings are saved back to this computer.
The UUMit remote access panel inside DSH
The plugin runs inside the DSH process and connects to the UUMit tunnel directly. It does not download or start any other program, and it does not open any port on your computer.
Beta. This is a preview release, published under the
betatag. Behaviour and configuration may change before 1.0.The plugin's interface is currently in Simplified Chinese. The button and option names below are translated, with the Chinese label in parentheses.
dsh web, DeepSeek Harness 0.2.1-rc.2 or later. The DSH desktop app does not run a web server and is not supported.dsh plugin --profile web add @uumit-ai/dsh-uumit-remote@beta
Then restart dsh web.
DSH installs plugins with pnpm, which by default skips releases published in the last 24 hours. Within a day of a new release, @beta can still give you the previous version; to get the new one right away, name the exact version, for example @uumit-ai/dsh-uumit-remote@0.1.0-beta.3.
If you use a registry mirror such as npmmirror and the install reports that no matching version was found, the mirror has not synced this release yet. Install straight from the official registry:
dsh plugin --profile web add @uumit-ai/dsh-uumit-remote@beta --registry=https://registry.npmjs.org/
To uninstall:
dsh plugin --profile web remove @uumit-ai/dsh-uumit-remote
The plugin is plain JavaScript with no runtime dependencies and no build step. The browser half (client.js) is written directly in the factory format the DSH module loader expects; React comes from the DSH page.
<dsh web address>/uumit-remote/.dsh under your UUMit address. Under Who can use it (谁能用), choose:
The DSH agent can help too: the plugin registers the tool uumit_remote_access (show status, start connecting, tell you where to manage it). The agent cannot change who can use the app.
Override the entry with id: uumit-remote in the profile's cordis.patch.yml. The whole entry is replaced, so omitted options go back to their defaults.
| Option | Default | Description |
|---|---|---|
apiBase | https://api.uumit.com | Platform endpoint. The UUMIT_API_BASE environment variable takes precedence. Non-HTTPS is only allowed for loopback and private addresses |
serviceName | dsh | Name of the registered app |
deviceName | <hostname> · DSH | Computer name shown on UUMit. Can also be set with UUMIT_DEVICE_NAME |
autoConnect | true | Bring a connected computer online when DSH starts. Never starts pairing on its own |
home | $DSH_HOME/uumit-remote | Local state directory |
Test-only switches: UUMIT_TUNNEL_INSECURE_TLS=1 skips verification of the tunnel node certificate, UUMIT_TUNNEL_CA_FILE sets a node CA file, and UUMIT_WEB_BASE sets the website base URL.
$DSH_HOME/uumit-remote/credentials.json, readable only by you, and never appears in logs or pages.Please report security issues privately through GitHub's security advisory page rather than public issues.
npm test # unit and integration tests
npm run test:frps # protocol conformance against a real frps 0.71.0
test:frps needs an frps 0.71.0 binary, set with FRPS_BIN or placed at test/e2e/.tools/frps; without it those tests are skipped.
Full local run (uses a temporary DSH_HOME, so your own ~/.dsh is untouched, and connects to no shared environment):
# 1. a real frps plus a stand-in platform
QA_API_PORT=18990 node test/e2e/qa-stack.mjs > /tmp/qa-stack.log
# 2. install the plugin into a temporary profile and start dsh web
DSH_HOME=/tmp/dsh-qa dsh plugin --profile web add link:$(pwd)
DSH_HOME=/tmp/dsh-qa UUMIT_API_BASE=http://127.0.0.1:18990 UUMIT_TUNNEL_INSECURE_TLS=1 dsh web --host 127.0.0.1 --port 3191 --no-open > /tmp/dsh-qa-web.log
# 3. nine acceptance steps: connect, open the real DSH through the tunnel, rejections,
# who can use it, invites and grants, the "Everyone" confirmation, off, disconnect and re-pair
node test/e2e/qa-flow.mjs /tmp/dsh-qa-web.log /tmp/qa-stack.log
Layout: client.js browser half (sidebar entry, in-page panel), src/frp/ frp client subset, src/control/ platform API and local state, src/tunnel.js tunnel management, src/agent.js orchestration, src/proxy/ loopback proxy and identity gate, src/ui/ local management API and fallback page, src/tool.js agent tool.