Work with DeepSeek on your projects in a local workbench.

A local desktop workbench for Windows and Linux, built on DeepSeek Harness.

DeepSeekGUI is a local AI workbench built on DeepSeek Harness. Choose a project folder and ask the assistant to read code, edit files, run commands, and browse the web. Inspect the project through Changes, Git, Worktrees, and Memory views, use dedicated tools for commits, pushes, and Pull Requests, and carry collaboration forward with global and project memory.

The distribution bundles its runtime. Configure a model API key to get started.

Not an official DeepSeek product. Built on DeepSeek Harness and independently developed, with no affiliation with or endorsement by DeepSeek. The upstream runtime and official Web UI are DeepSeek's work.

Current release: v1.1.0. The local Workbench, Git / PR tools, global and project memory, and desktop notifications are available. The Workbench extends the official Harness client through plugins and uses Harness sessions, tools, and permissions.

Download

The Windows installer installs to your user account and bundles its runtime. Linux uses a separate AppImage distribution; download and verification details are on the v1.1.0-linux.1 release page.

Windows installation: The installer is not code-signed, so SmartScreen may report an unknown publisher. After checking the download source and SHA256, choose “More info” → “Run anyway” to continue.

Get-FileHash .\DeepSeekGUI-Setup-1.1.0.exe -Algorithm SHA256

Quick start

1. Install DeepSeekGUI and open it.
2. Go to Settings → Models and enter your DeepSeek API key.
3. Choose a model; select one with vision support if you need image input.
4. Return to the home screen and choose a workspace folder.
5. Start a session and describe the task. Review file diffs in Changes and repository status and operation results in Git.
6. Optionally save collaboration preferences in Settings → Global Memory and inspect or organize project memory in the conversation's Memory view.

See the quick-start guide for a full walkthrough.

Why DeepSeekGUI

Visible project state. Inspect file changes, branches, commits, and worktrees beside the conversation without requesting the model for each status check.

Lasting project knowledge. Global memory stores cross-project preferences; project memory records decisions, conventions, and corrections. Each is managed separately.

Reviewable operations. Git, PR, and browser result cards show summaries and details. Commits and pushes use Harness approvals, and you choose the permission mode.

Visible browsing. The built-in browser shows the pages the assistant visits, with sensitive interactions subject to Harness approvals.

Local storage, network access as needed. Sessions, credentials, settings, and memory are stored locally. Model requests go to your configured provider.

Built on Harness. Use native profiles, plugins, hooks, and the CLI, with one runtime shared by the Workbench and conversations.

Screenshots

Dark theme	Light theme

One local workbench, two themes. Click an image to view it at full size.

Open a webpage beside the conversation and inspect the assistant's browsing actions and results, with both the conversation and page in view.

Configure models and access Harness desktop controls, local plugin management, diagnostics and feedback, and global memory from the same settings window.

Inspect the current branch, remote configuration, recent commits, and Git operations recorded in this session.

Keep project background, confirmed decisions, and collaboration conventions together. Read them as Markdown or ask the assistant to organize them.

Users edit and save cross-project preferences for the assistant to read; project facts are managed separately in project memory.

Workbench features

Local projects and Git collaboration

• Changes view — Inspect staged, modified, new, and conflicted files, open per-file diffs, copy paths, or reveal files in the file manager.
• Git view — Inspect branches, remote sync status, recent commits, and commit, push, and PR results from loaded conversation history.
• Worktrees — Inspect registered worktree branches and changes, including paths modified in multiple worktrees.
• Git / PR tools — Request diffs, staging, unstaging, discarding unstaged changes to tracked files, commits, push previews, pushes, and PR creation through the conversation, with dedicated result cards.
• Local inspection — Views read workspace state on demand without model requests. Workspace paths support click-to-reveal, and the built-in terminal can follow the current session directory.

Memory and collaboration rules

• Global memory — Edit cross-project preferences and collaboration instructions in settings; the assistant has read-only access.
• Project memory — The assistant maintains project facts in <folder name>.memory.md in the workspace. The Memory view supports Markdown reading and requests to organize its contents.
• Rule templates — Initialize a global AGENTS.md on the managed home's first launch and generate project templates on request, preserving existing files.
• Recorded context — Read both memory layers when a session loads and record the content used with the Harness session context.

Models and desktop tools

• Models and image input — Configure DeepSeek or custom model providers and send screenshots and images to vision-capable models.
• Sessions and permissions — Start and resume conversations in project folders, inspect tool execution, and control operations through Harness permission modes and approvals.
• Browser and terminal — Inspect pages in a visible browser and use the current Harness environment through the built-in DSH Terminal.
• Desktop notifications — Receive pending approval and question notices, plus background-job completion or failure notices; click to open the corresponding conversation.
• Profiles and plugins — Switch Harness Homes and Profiles, manage compatible plugins, and inspect configuration and runtime status.
• Desktop integration — Chinese and English interfaces, system tray, update checks, and local diagnostics.

See the v1.1.0 release notes for the complete version changes.

Documentation

The docs also include upstream Harness tutorials and plugin-authoring reference.

Data and privacy

Managed credentials, settings, sessions, and global memory are stored in the local application data directory, which defaults to %APPDATA%\DeepSeekGUI\dsh on Windows. Project memory lives in <folder name>.memory.md in the selected workspace. Model requests send task context to your configured provider; browsing, Git / PR operations, plugin management, and update checks also contact their respective network services.

Logs redact credential-like content, and diagnostics stay local. The Windows uninstaller asks whether to delete application data; upgrades preserve it. Check diagnostics and project memory for private content before sharing or committing them.

Build from source

Run DeepSeekGUI from source

Requires the Node.js version declared by the repository and pnpm:

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

Build the Windows distribution:

pnpm run build:desktop-dist

See DeepSeekGUI Desktop for packaging details.

Run Harness from npm

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

npx @deepseek-ai/dsh web

Opens http://127.0.0.1:3080 in your browser.

Run Harness from source

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

pnpm install
pnpm run build
pnpm dsh web

Contributing and support

• Report bugs and feedback through DeepSeekGUI Issues.
• Read CONTRIBUTING.md before sending a pull request.
• For upstream Harness questions, use DeepSeek Harness Discussions.

License

Two scopes:

• Upstream Harness code stays under DeepSeek's MIT License.
• DeepSeekGUI original work is source-available under the PolyForm Perimeter License 1.0.1. Personal, educational, research, hobby, and internal business use are fine. Building a competing product requires a separate license from See-Sol-Lab.

The root LICENSE explains how the scopes apply. Read DeepSeekGUI licensing and third-party notices before redistributing.

DeepSeekGUI is the public release repository. Day-to-day development happens in a private repo; releases publish the product tree.