跳到主要内容

dsh-palm

已验证

@eternalloveone/dsh-palm · v1.5.3 · Apache-2.0 · Web 界面

掌上 dsh — the standalone mobile surface for the dsh web GUI: scan-to-pair device trust, the /m/ phone UI, the /m/api RPC channel with realtime SSE mux bridge, and a polished desktop pairing panel. Extracted from dsh-remote-web-ui (M1, behavior-identical)

安装

dsh plugin add @eternalloveone/dsh-palm

用 dsh --profile default --dump-config 确认 layer 已生效 —— 参见安装指南。

源码

标签

作者

说明文档

dsh-palm

dsh in your palm — the standalone mobile surface for the dsh web GUI: scan-to-pair device trust, the /m/ phone UI, the /m/api RPC channel with a realtime SSE mux bridge, and a polished desktop pairing panel.

Derived from dsh-remote-web-ui — see NOTICE for attribution.

Install

Requires dsh >= 0.1.1-rc.1.

dsh plugin --profile web add @eternalloveone/dsh-palm

Already-paired devices keep working after switching install sources.

Highlights

  • Standalone /m/ mobile UI — an independent phone bundle, not a CSS-injected adaptation
  • Desktop-phone live sync — one shared host event stream (measured: loopback 4 ms / public tunnel 9 ms / Tailscale 13 ms median)
  • SSE mux bridge with polling fallback — stall detection (36 s) arms adaptive history polling; events are never lost
  • Windowed streaming renderer — inline-markdown tail preview, no typewriter cursor, collapsible reasoning blocks
  • Interactive diff cards, code actions, command cards, realtime approval panels, image attach, voice transcription, plugin market
  • PWA + offline outbox + gzip-compressed API responses — weak-network friendly
  • Completion notifications — task-finished and long-reply alerts through three layers: in-app system notifications (SSE), Web Push (VAPID), and third-party channels (Server酱 / Bark / Telegram) for when the app is closed; thresholds and cooldowns are configurable from the phone, with per-kind gates (plan-complete / background-task / long-reply) and a lock-screen privacy toggle
  • Global search with message-level locate — search workspaces and every session from the home page, or the current workspace from the session list; hits open the chat and scroll to the matched message with a one-shot highlight (Chinese short words covered by a substring backfill)
  • Pending-message queue dock — messages sent while a turn is running queue in the host and show as a dock above the composer (desktop QueueDock parity): editable, removable, or steered in as an interrupt
  • Global run overview — a full-screen cross-session view of running sessions and live background jobs, reachable from the home page's quick chip with a live badge
  • In-chat file & image preview — file-path links open a bottom sheet: markdown renders formatted, HTML renders in a sandboxed iframe, code highlights, images display inline; message images open a full-screen lightbox
  • Per-provider usage & balances — one settings card per provider: consumed-quota meters, account balances and OpenRouter's spent-vs-limit, refreshed on demand
  • Six-digit pairing code — type a code on the phone instead of scanning
  • Three-step pairing wizard — configure → pair → use, with tunnel detection (Tailscale one-click, frp entry from frpc.toml), reachability-checked saving, and a clean device-management view once paired
  • Workspace-native theming — the panel follows the system light/dark scheme via prefers-color-scheme

Full feature list, measured data and architecture docs: see the repository README.

Remote access setup

The desktop pairing panel (the phone icon in the sidebar) walks you through three steps: configure → pair → use. To reach this computer from your phone you need an address the phone can reach:

  • Same network — start dsh web bound to your LAN address; the phone pairs over Wi-Fi with zero configuration.
  • Tailscale — install Tailscale on this computer and your phone; the panel detects it and fills your tailnet address with one click.
  • Cloudflare Tunnel / frp — run a tunnel to this machine and enter its public URL in the panel's public-address card. Saving verifies reachability first, so a dead tunnel is caught before it is persisted.

A full walkthrough with a worked frp topology (server frps + nginx TLS, client frpc, panel configuration, verification, and FAQ) lives in the remote access guide.

License

Apache-2.0 — see LICENSE.