Harness Desktop

A desktop home for DeepSeek Harness with model routing, plugins, mobile access, and verified updates.

Stars
★ 10
Last updated
today
License
MIT
Primary language
JavaScript

At a glance

Works with
Platform-specific
You'll need
DeepSeek Harness 0.1.2-alpha.5Windows 10/11 x64 for the formally supported desktop releaseNode.js 24, npm, and Git for developmentShell / CLINetwork accessLocal filesystemMCP Server
Typical use
A Windows 10/11 user who wants an installed or portable DeepSeek Harness desktop app while retaining the official workbench as the only main UI.
Main limitation
It is community maintained and not endorsed by DeepSeek; core operation depends on the official DeepSeek Harness and its runtime contracts.
Source review
82/100 · Good

What does this agent do, and when should you use it?

Harness Desktop is a community-maintained Electron shell for the official DeepSeek Harness Web UI, which remains the product's sole primary interface and agent core. It starts the local Harness Runtime and adds main-model and subagent routing, a DSH plugin marketplace, managed Skills, an integrated terminal, workspace previews, schedule visibility, themes, and a desktop pet. Users can import files into the workspace `uploads/` directory, prepare reviewable edits through the official `read` and `edit` tools, and preview common document and media formats in a right-side workspace. Paired mobile devices can reach the current workbench over a LAN, native WebRTC P2P, or an end-to-end encrypted WSS/443 fallback; Android has a signed preview client, while iPhone and iPad use the Safari workbench. Windows 10/11 x64 is the formally supported stable target, while the macOS DMGs remain public previews pending validation on real Apple hardware. It is aimed at users who want DeepSeek Harness's existing interaction and permission model with stronger desktop integration, mobile continuity, and cryptographically verified delivery.

The application launches the official DeepSeek Harness Web UI and local Runtime inside an Electron desktop shell. Its Electron bridge supplies windowing, installation, updating, and desktop features; the Renderer has no Node.js privileges, and the WebView may access only the local Harness Runtime. Providers, models, and credentials are configured in the official Harness settings, and the shell does not keep a second copy of Provider secrets; the main model and subagents may share a model or use separate selections. The DSH marketplace discovers, installs, and updates plugins, while managed Skills use $ triggers and @ remains the file-reference syntax. MCP settings manage stdio and Streamable HTTP connections and retain credential references rather than raw secrets. User-selected files are imported into uploads/, ordinary workspace files can be downloaded, and the official read and edit tools prepare drafts for review; the right-side workspace provides read-only previews for text, source code, HTML, images, audio, video, and PDF files. Schedule monitoring consumes official append-only events with ETag/304 and since-delta refreshes, falling back to one authoritative full replay after a gap, rewind, or generation fork. Desktop delivery uses an Ed25519-signed manifest, HTTPS, declared file sizes, SHA-256 verification, source fallback, component health checks, and automatic rollback. Mobile Sync pairs trusted devices by QR code and carries workbench state and constrained uploads over LAN, native WebRTC P2P, or an end-to-end encrypted WSS/443 relay.

  1. A Windows 10/11 user who wants an installed or portable DeepSeek Harness desktop app while retaining the official workbench as the only main UI.
  2. A multi-model user who needs separate model choices for the primary model and subagents while preserving running, resumable, and read-only historical tasks.
  3. A Harness user who wants in-app DSH plugin management, $-triggered managed Skills, and @ references to workspace files.
  4. Someone who needs to continue a workbench session from Android or a mobile browser, upload constrained documents, and switch between local and encrypted remote connectivity.
  5. A technical user who wants MCP stdio and Streamable HTTP configuration, bounded terminal access, and workspace file previews in one desktop application.
  6. A deployment-conscious user who requires signed manifests, SHA-256 package checks, rollback, and preservation of themes, plugins, and routing settings across Harness updates.

How do you install or deploy this agent?

For routine Windows use, download and run the current v1.0.60 stable installer; it installs for the current user and does not require administrator privileges. A portable Windows executable is also provided. Windows 10/11 x64 is the formal stable target; Apple Silicon and Intel macOS DMGs are public previews pending acceptance on real Apple hardware.

Scoop users can install from the project's bucket:

scoop bucket add harness-desktop https://github.com/baiyuscc13724-max/scoop-harness-desktop
scoop install harness-desktop/harness-desktop

Source development requires Node.js 24, npm, and Git:

npm install
npm run dev

Run the documented checks and distribution build before submitting changes or producing packages:

npm run verify
npm run verify:release
npm run dist

On first launch, add a provider, model, and the corresponding credentials in the official Harness settings. The desktop shell does not retain a duplicate copy of Provider keys.

How do you use this agent?

  1. Launch the installed or portable application, then add the chosen provider, model, and required credentials in the official Harness settings.
  2. Select a workspace and start a new session. Configure the main model and subagents separately when different routing is needed.
  3. Use the top palette control for desktop themes or open the Deep Whale desktop pet. Plugins, Skills, models, and general preferences remain in the official settings page.
  4. Explicitly import files into the workspace uploads/ directory and reference them with @. Use the official read and edit tools to prepare edits for review.
  5. Configure MCP connections as stdio or Streamable HTTP in settings. Starting a local MCP process requires explicit confirmation.
  6. For mobile use, open Mobile and Remote Sync in settings and scan the pairing code once. LAN connectivity is preferred; for remote use, configure a personal credential-free wss:// endpoint for WebRTC signaling and encrypted relay fallback. The computer must keep Harness Desktop running.

What are this agent's strengths and limitations?

Pros
  • It preserves the official DeepSeek Harness workbench, sessions, permissions, and agent core instead of creating a second sidebar or duplicate settings system.
  • It combines DSH plugins, managed Skills, main-model/subagent routing, MCP management, bounded terminals, and multi-format workspace previews.
  • The update chain includes Ed25519 manifest verification, HTTPS on every hop, size and SHA-256 checks, fallback sources, health checks, and automatic rollback.
  • Mobile Sync covers LAN, native WebRTC P2P, and end-to-end encrypted WSS/443 fallback with trusted-device pairing.
  • The Renderer lacks Node.js privileges, the WebView is restricted to the local Runtime, and external links pass through constrained IPC to the system browser.
Limitations
  • It is community maintained and not endorsed by DeepSeek; core operation depends on the official DeepSeek Harness and its runtime contracts.
  • Formal stable support currently centers on Windows 10/11 x64. macOS lacks final validation on real Apple hardware, and no unsigned iOS IPA is distributed.
  • Remote mobile use requires the computer to remain online and depends on network availability; a personal WSS relay also requires the user to supply and configure a wss:// endpoint.
  • Development requires Node.js 24, npm, and Git, while publishing is gated by verification, cloud builds, signing, and cross-source checks.
  • The Deep Whale artwork is licensed separately under CC BY-NC-SA 4.0 and cannot be used commercially, even though the desktop shell code uses the MIT License.
  • Once authorized, Computer Use can control the entire Windows virtual desktop and does not apply content-level sensitive-action filtering, making the permission scope broad.

How does this agent compare with similar options?

Compared with using the official DeepSeek Harness Web UI alone, this project keeps that UI and agent core but adds Electron packaging, installation and signed updates, plugin and Skills management, model routing, a desktop pet, terminal access, workspace previews, and mobile pairing. On iPhone and iPad, it deliberately uses the live Safari workbench instead of distributing an unsigned IPA that users could not publicly install without an Apple Developer membership. EasyTier and Tailscale are optional mobile connectivity paths; the documented default is LAN first, native WebRTC P2P for remote connections, and encrypted WSS/443 fallback.

Key facts side by side with the most closely related agents.

Agent Source review Stars Updated Language Full support on
Harness Desktop This agent 82 · Good ★ 10 today JavaScript —
DeepChat 66 · Some gaps ★ 6.3k 4d ago TypeScript OpenAI API · Claude API
Dive AI Agent 52 · Major gaps ★ 1.8k 1mo ago TypeScript ChatGPT · OpenAI API · Claude API
AnythingLLM 48 · Major gaps ★ 66k today JavaScript OpenAI API · Claude API

How does FollowAgents rate this agent?

FollowAgents source review · FARS-2.1
Good
82/ 100 5-point scale 4.1 / 5
Trust 24/29
Reliability 11/14
Adaptability 16/18
Convention 15/18
Effectiveness 10/13
Verifiability 6/8
Why each dimension lost points
Trust24 / 29 · 4.1/5

SECURITY.md documents renderer isolation, constrained preload/IPC surfaces, loopback services, ephemeral credentials, signed updates, hash checks, credential references, and a private reporting path. The README also clearly disclaims official status and attributes third-party artwork, supporting strong transparency, external-effect disclosure, rollback, and attribution scores. Deductions apply because Computer Use can control the entire virtual desktop after one authorization, persistent authorization may return at startup, and there is no per-action confirmation; the LAN mobile bridge still uses unencrypted HTTP; and although many dependencies and Actions are pinned, some npm ranges remain and no lockfile, vulnerability report, or complete supply-chain inventory is included.

Reliability11 / 14 · 3.9/5

The README, security policy, package metadata, and workflows mostly describe a coherent product and release model. CI contains explicit version, tag, signing, certificate, architecture, hash, and fail-closed checks with useful failure messages. Deductions reflect mild tension between the claim that stable artifacts are Windows-only and the v1.0.60 macOS/Android download table, the unreleased 1.0.61 source version, reliance on alpha core packages, and the inability of the supplied static evidence to establish continuing dependency availability.

Adaptability16 / 18 · 4.4/5

The evidence distinguishes installed and portable desktop use, mobile access, teams, plugins, terminal, MCP, browser, and Computer Use scenarios, while clearly separating the upstream core from removable desktop enhancements. Team formation, skill/file-reference syntax, and privileged-feature authorization have precise triggers. Environment fit is reduced because Windows is the formal target, macOS still lacks real-hardware acceptance, iOS distribution is constrained, and the Linux build configuration has no corresponding support guidance.

Convention15 / 18 · 4.2/5

The README has clear download, feature, quick-start, boundary, development, licensing, and bilingual overview sections. Installation methods, requirements, stable-versus-candidate status, platform limitations, and the full MIT license are supplied. Deductions apply because the evidence omits the referenced release-notes content and lacks a developed FAQ or troubleshooting examples; naming spans Harness Desktop, DeepSeek Harness, DSH, and separate mobile versions; and maintenance is attributed only to contributors, repository issue/advisory channels, and an unverified account without ownership or response commitments.

Effectiveness10 / 13 · 3.8/5

The product adds verified updates, plugins, mobile pairing, routing, desktop interaction, and security gates around the upstream workbench, offering substantial marginal value over the bare web interface. Downloads and a three-step start improve usability. Scores are reduced because the broad feature surface includes experimental or preview capabilities, Computer Use and remote/mobile paths impose meaningful setup and security costs, and no statically verifiable user-outcome data or resource-cost benchmarks are supplied.

Verifiability6 / 8 · 3.8/5

Several claims align across sources, including pinned upstream versions, Electron isolation, signed publishing, Android certificate/hash verification, and macOS virtual testing. The project also carefully separates candidate, stable, preview, unvalidated, and not-reproduced states. Deductions apply because many detailed claims about runtime behavior, teams, memory, browser controls, and recovery appear only as README or policy assertions; the supplied evidence lacks their implementation files, test outputs, and referenced release-note content, limiting independent cross-source corroboration.

Risks and how to mitigate them
  • Persistent Computer Use authorization can return at startup and grants control of the full Windows virtual desktop without per-action confirmation or content-sensitive filtering.
  • The LAN mobile workbench currently relies on an explicitly enabled HTTP bridge and should not be used on untrusted public Wi-Fi.
  • Version 1.0.61 is an unpublished candidate; stable downloads remain at 1.0.60, and macOS has not completed formal validation on real Apple hardware.
  • Some core dependencies are alpha releases, and the supplied evidence contains neither a lockfile nor dependency-vulnerability audit results.
  • The publisher is not verified by the FollowAgents enterprise registry; this means the identity is unknown, not malicious.
Evidence confidence: Low Reviewed Sep 24, 2026 Reviewed revision 2d3deaa539fe
See the full review method →

FAQ

Is this an official DeepSeek application?
No. It is a community-maintained open-source project and is not endorsed by DeepSeek. Sessions, workspaces, permissions, and the agent core come directly from the official DeepSeek Harness.
Does installation require administrator access or duplicate my model credentials?
The Windows installer operates for the current user and does not require administrator privileges. Provider models and credentials are managed by the official Harness settings, and the desktop shell does not store a second copy of Provider keys.
Are macOS and mobile clients production-supported?
The formal stable target is Windows 10/11 x64. macOS DMGs and the signed Android client are public previews; macOS still awaits real-hardware validation, and iPhone/iPad users access the workbench through Safari.
What happens when direct mobile connectivity fails?
The application prefers LAN access and uses WSS signaling to negotiate native WebRTC P2P remotely. If direct connectivity is restricted, it falls back to the same end-to-end encrypted WSS/443 blind relay. The desktop must remain running, and the relay does not store or decrypt Harness data.
Does the desktop pet inspect conversations or the screen?
No. Deep Whale responds to structured task rhythm and may retain local preferences, daily progress, and completion streaks, but the documented behavior excludes reading conversation text or screen contents.
View on GitHub ↗ Install ↓

Compare agents like this one

The same FARS review applied across the shortlist this agent qualifies for.

Related agents