dsh-web-remote-frp

DSH runs locally by default, so continuing a conversation from a plane, a cafe, or a client office was never realistic. The original dsh-web-remote leaned on Cloudflare Quick Tunnel, which hands you a fresh random *.trycloudflare.com address on every restart and leaves throughput at the mercy of a third-party relay. dsh-web-remote-frp replaces that channel with a self-hosted frp tunnel (frpc pointing at your own frps server), giving you a permanent http://server:port or custom-domain URL, full control over latency and concurrency, and tcp, http, or https proxy modes to match the use case.

Beyond the tunnel itself, the plugin folds day-to-day operations into a single sidebar panel. LAN direct access (HTTP plus HTTPS with auto-generated self-signed certificates) and the public frp channel each have an independent on/off switch with no cross-interference. A fresh random token is generated on every boot and protected via HttpOnly cookies. Reverse-proxy gzip compression keeps long conversation histories loading fast. QR codes are rendered entirely in-browser with zero external dependencies. The settings tab lets you paste PEM certificates, generate a self-signed cert for your domains in one click, auto-detect the OS and architecture to grab the latest frpc binary, and save changes with a single button—no YAML spelunking required.

The six-channel bot bridge completes the picture: WeChat, QQ via NapCat, Telegram, DingTalk, Feishu, and WeCom all share one command router. A single message in any chat app returns the remote URL, switches models, or queries sessions, and the AI reply comes straight back. Built for developers and power users who already run a small VPS with a public IP, want a stable address they can bookmark, and prefer to drive DSH from the chat tools they already live in.