DeepSeek Harness PWA for Mobile Access

What changed

A new Progressive Web App (PWA), named dsh-pwa, has been developed to provide mobile access to the DeepSeek Harness (dsh) platform. This PWA mounts at the /m path on a dsh web server and offers functionalities such as session listing, real-time streaming chat, approvals, agent questions, new session creation, and image messaging. A key design choice is its PWA nature, which eliminates the need for users to install a native application on their iOS or Android devices; instead, users can open it in mobile Safari or Chrome and add it to their home screen for a full-screen app-like experience.

The dsh-pwa is positioned as a zero-install alternative to native mobile applications, specifically targeting users who need functionality on both iOS and Android without app installation. It contrasts with the saya-ch/dsh-mobile native Android app, which offers system notifications and certificate-pinned device pairing, and the official web UI which is desktop-first. The PWA inherits its remote access capabilities from the dsh web server, supporting LAN, Tailscale, or any reverse proxy configuration. However, it notes limitations such as the absence of push notifications on iOS PWAs due to platform constraints.

Key features of the dsh-pwa include a session list with workspace grouping, search, pull-to-refresh, and an "needs attention" filter. The streaming chat supports optimistic sending, queued message visibility, per-day dividers, timestamps, code-copy buttons, and a full-screen image viewer. Approvals and agent questions are presented as tappable cards, with dangerous commands requiring a double confirmation. Users can send images from their camera, photo library, or clipboard, with automatic compression to model limits. New sessions can be created with an agent-preset picker. Additional features include haptics, dark/light themes, per-session draft autosave, and a connection status indicator with manual reconnect. The desktop GUI also receives an update with a "手机端" (mobile) entry in its settings, displaying the phone URL for easy access.

Installation involves adding dsh-pwa as a dependency to a dsh web profile's package.json, running npm install, and then starting the dsh web server with appropriate --trusted-host configurations for remote access. The PWA works by serving static files from the web/ directory at /m and communicates directly with DSH's /api endpoint, using the same protocol as the desktop GUI. This design minimizes business logic duplication and ensures the PWA moves with DSH version updates. The project is developed in Vanilla JS with no build step or framework, aiming for simplicity and ease of contribution.

Why it matters for builders

This PWA offers AI builders a convenient way to interact with their DeepSeek Harness instances directly from their mobile phones, without the overhead of installing native applications. It enables continuous management of AI agent sessions, real-time chat interactions, and approval workflows, even when away from a desktop environment. The direct API communication ensures that the mobile interface remains synchronized with the core DSH functionality.

Practical impact

AI builders can now leverage their mobile devices for immediate oversight and control of their DeepSeek Harness deployments. This includes responding to agent queries, approving critical actions, and monitoring ongoing sessions from anywhere with an internet connection. The quick setup via npm and browser access means builders can start using the PWA with minimal friction. Developers interested in contributing can engage with the project's Vanilla JS codebase and contribute to roadmap items like session management or web push notifications.

Caveats and source limits

The dsh-pwa currently lacks push notification support on iOS due to PWA platform limitations. While it aims for seamless integration, the project is still in a developer preview phase, and its API may undergo breaking changes, requiring corresponding updates to the PWA. Offline functionality is not supported, as it requires a live connection to the dsh server. The security model relies on the dsh web server's existing trusted-host fence, meaning exposure should be limited to trusted networks to prevent unauthorized access to the agent. The project is open-source, with a MIT license, and contributions are welcomed via pull requests.