@deepseekharness-mobile/companion
v0.3.1
Published
DSH host plugin: WebSocket bridge, QR pairing and device tokens for DSH Mobile
Maintainers
Readme
Features
Install
dsh profile add @deepseekharness-mobile/companionThe profile reads the bundle's cordis.patch.yml, mounts the plugin and serves the embedded
PWA on 127.0.0.1:6768. Restart DSH afterwards, run /mobile in a session and open the link
on the phone; the PWA installs from the browser menu.
The listener is loopback-only by design: the phone reaches it through the tailnet name with
tailscale serve, which provides HTTPS and a secure context. The full path, with the usual
problems, is in
docs/phone-setup.md.
What the phone gets
- Live transcript with paged history, separated reasoning, markdown and file cards.
- File viewer for markdown, text, images, PDFs and Office documents — the host converts the document and the app draws its pages, so a phone shows it instead of downloading it. Files are read inside the session workspace only.
- Turn usage: context over the window, cache-hit ratio and decode speed under the model.
- Questions and approvals, including the blocking
ask_user_question, in an inline card. - Agent activity: goal and round, running subagents and open tasks in a floating panel that does not shrink the conversation.
- Slash commands from the composer, with the result outside the model transcript.
- Model providers: test a key and connect it; the key is stored on the host and never comes back, and endpoints, headers, model overrides and OAuth stay on the desktop.
- Paired devices: last seen, revoke and forget, with the host revoking first.
- Sessions, folders, model choice, write and cancel, and an installable PWA with four locales.
The full feature tour, the architecture and the security model live in the repository README.
Security
- Loopback only. The listen address is a constant, not an option; the tailnet name is the only supported path and LAN access is not implemented.
- Pair before anything. The QR carries a single-use code in the URL fragment, valid for 10 minutes and never written to a log; redeeming it creates a device token stored as a hash.
- One token per device. Revoking one cuts its sockets and does not affect the others.
- The host decides. Capabilities are negotiated in
hello.ok; the client cannot see or do what the server does not send.
Documentation
- Repository — the product, the features and the screenshots.
- Phone setup — Tailscale, pairing and the usual problems.
- Architecture — why it is built this way.
@deepseekharness-mobile/protocol— the wire contract, also on npm.
License
MIT
