omdsh-plugins/omdsh-remctrl

README excerpt

omdsh-remctrl English 中文 Remote control for the DeepSeek Harness: a second front door on its own port, behind device pairing and a tiered method allowlist, so a phone on your tailnet can watch a session, approve what it asks for, and hand it new work. Status: M0 — the door and the lock, and nothing behind them yet. What a phone can do today is pair against a running harness and see itself reported as paired; reading sessions, the live stream, approvals, and sending work are M1 through M4. The design and the reasoning behind it are in DESIGN.md; the harness APIs it stands on are in RESEARCH-harness-host-api.md. Both are written in Chinese. What it adds Surface Where it comes from A second HTTP listener on port 3081 , on loopback or a tailnet address src/server.ts — its own node:http server, never ctx.webServer , whose runtime schema admits only 127.0.0.1 and 0.0.0.0 A phone page that pairs and says so src/mobile/assets.ts — three assets at / , /app.css and /app.js , none of them inline, so the page serves under a strict CSP /pair and /session The token door: a six-digit code redeemed once, and a bearer token that proves the device from then on A loopback-only control channel — mint,…

Category