Back to home@See-Sol-Lab

DeepSeekGUI

一个非官方的基于dsh的GUI。An unofficial Windows desktop workbench for DeepSeek Harness.

Stars
1
Language
TypeScript
Created
Aug 17, 2026
Updated
Aug 27, 2026
GitHub repo

Introduction

DeepCode — a harness-first desktop workspace for agentic coding

DeepCode

English | 中文

Use it like Codex. Inspect it like a lab. Extend it like Harness.

A DeepSeek-native Agent Workbench for Windows, powered by DeepSeek Harness.

Latest release Downloads Windows 10 and 11 x64 Source available

DeepCode turns DeepSeek Harness into a complete Windows product: install it, connect DeepSeek, choose a workspace, and let an agent inspect, edit, browse, run tools, and explain its work. Harness remains the only runtime and source of session, model, credential, permission, tool, memory, compaction, and plugin state.

Unofficial product: DeepCode is not affiliated with or endorsed by DeepSeek. The upstream Harness runtime and official Web UI are DeepSeek's work.

Download

PlatformDownloadRequirements
WindowsDownload the installerWindows 10/11, x64

DeepCode installs for the current Windows user without administrator rights and includes its own Harness runtime, Node.js, and pnpm.

Or download the latest installer and checksum from PowerShell with GitHub CLI:

gh release download --repo See-Sol-Lab/DeepSeekGUI --pattern 'DeepCode-Setup-*.exe' --pattern 'SHA256SUMS.txt' --clobber

DeepCode V1 is not code-signed, so Windows SmartScreen may show an unknown-publisher warning. Download SHA256SUMS.txt from the same release and verify the installer before running it:

Get-FileHash .\DeepCode-Setup-1.0.0.exe -Algorithm SHA256

Continue only when the printed hash matches the release manifest exactly, then run Start-Process .\DeepCode-Setup-1.0.0.exe. See the installation and troubleshooting guide.

Quick start

  1. Install and launch DeepCode.
  2. Open Settings → Models and enter your DeepSeek API key.
  3. Select a model. Choose an image-capable model when the task includes screenshots or other visual input.
  4. Return to the home page and choose a workspace folder.
  5. Start a session and give the agent one concrete outcome.
  6. Review tool approvals and the resulting file changes.

The DeepCode quick-start guide walks through the complete first session.

Why DeepCode

Harness-nativeProfiles, sessions, tools, credentials, permissions, memory, compaction, hooks, and plugins stay in the native Harness composition. DeepCode does not create a second agent runtime.
DeepSeek-firstDeepSeek models, reasoning, image input, and Harness behavior are first-class product paths rather than compatibility afterthoughts.
A real Windows productOne-click current-user installation, resident tray, model settings, DSH Terminal, updates, feedback, diagnostics, and an uninstall data choice.
Observable and recoverableLive Harness status, explicit targets, redacted diagnostics, last-known-good Profile recovery, and protected plugin changes make failures understandable and reversible.
Safer executionSandbox is the recommended default, approvals remain owned by Harness, Full Access always carries an explicit warning, and browser submissions require approval.
ProgrammableUse arbitrary compatible Harness Profiles and Cordis plugins, inspect the active composition, and keep the official DSH CLI close at hand.

Product tour

A completed DeepCode coding task that creates and runs a JavaScript file

Work with code, files, and images

Choose a workspace, resume durable sessions, attach images to a vision-capable model, stream results, and review tool activity without leaving the desktop application.

A DeepCode vision session correctly describing an attached interface screenshot

Give the agent a real browser

DeepCode's built-in browser uses visible Microsoft Edge, checks navigation targets and redirects against SSRF rules, keeps physical mouse and keyboard control with the user, and routes sensitive submissions through Harness approval.

A DeepCode session using the built-in browser to inspect a public webpage

Inspect and control the Harness

Switch Managed or Existing Homes, select Profiles, inspect effective plugin state, manage compatible plugins through the official CLI path, and recover a failed change without hiding what happened.

DeepCode Settings with general, model, plugin, and agent preset controls

What ships in V1

  • Windows 10/11 x64 installer and portable unpacked build.
  • DeepSeek and custom model configuration through Harness settings.
  • Text and image input for models that advertise the corresponding modality.
  • Workspace-based coding sessions with native Harness tools and approvals.
  • Managed and Existing Harness Homes with Profile discovery and switching.
  • Plugin Manager with target confirmation, streamed output, post-checks, and protected recovery.
  • Built-in real-browser tools and a visible Browser Panel.
  • Sandbox, Full Access, Read-only, and Custom permission reporting.
  • DSH Terminal with private runtime shims and no system PATH modification.
  • Update verification, local diagnostics export, feedback, system tray, and bilingual Chinese/English desktop copy.

DeepCode V1 is tested on Windows x64. It is not code-signed and does not ship macOS or Linux builds, an account system, automatic startup, or a plugin marketplace.

Documentation

GuideWhat it covers
Quick startInstall, connect DeepSeek, choose a workspace, and finish the first session.
Models and visionAPI keys, model selection, image input, and custom providers.
Workspaces and sessionsWorkspace scope, durable sessions, attachments, review, and tray behavior.
Profiles and pluginsManaged/Existing Homes, Profile switching, plugin operations, and recovery.
Permissions and approvalsSandbox, Full Access, approvals, Existing Home behavior, and browser permissions.
Desktop toolsBrowser, DSH Terminal, updates, diagnostics, feedback, and lifecycle.
Data and troubleshootingData locations, privacy, uninstall behavior, common failures, and support.

The documentation website also retains the upstream Harness development tutorials and reference material for plugin authors and advanced users.

Data and privacy

DeepCode stores its Managed Harness Home under %APPDATA%\DeepCode\dsh. Credentials, settings, sessions, Profiles, and plugins stay in that Home unless the configured model provider or a tool transmits content required by the task.

Service logs redact credential-shaped text. Diagnostics bundles are created locally and never uploaded automatically. Review crash dumps before sharing them because they can still contain local paths or memory fragments.

Uninstall asks whether to remove %APPDATA%\DeepCode. Keeping it preserves credentials, settings, sessions, and Profiles for a later reinstall.

Build from source

Run DeepCode Desktop from source

DeepCode development requires the Node.js version declared by the repository and pnpm:

git clone https://github.com/See-Sol-Lab/DeepSeekGUI.git
cd DeepCode
pnpm install
pnpm run build
pnpm run dev:desktop

Build the Windows distribution with:

pnpm run build:desktop-dist

See DeepCode Desktop for engineering details and packaging verification.

Run Harness from npm

Install Node.js, then start the upstream Web UI with:

npx @deepseek-ai/dsh web

The command opens http://127.0.0.1:3080 for a local launch.

Run Harness from source

The public DeepCode tree contains the upstream Harness source used by the desktop build:

pnpm install
pnpm run build
pnpm dsh web

Contributing and support

License and upstream relationship

This repository combines two licensing scopes:

  • Upstream DeepSeek Harness code and upstream-derived material remain under DeepSeek's MIT License.
  • Original DeepCode desktop and product work is source-available under the PolyForm Perimeter License 1.0.1. Personal, educational, research, hobby, internal business, and other permitted uses are allowed; providing a competing product requires a separate license from See-Sol-Lab.

The root LICENSE is a scope notice, not a single repository-wide license grant. Read DeepCode licensing and third-party notices before redistributing the software.


DeepCode is the public release repository. Day-to-day development happens in a separate private repository; releases publish the product tree rather than the private development history.