What is DeepSeek GUI?
DeepSeek GUI is a Windows AI workbench based on DeepSeek Harness. Version 1.2.0 retains account sign-in, usage views, skills, the browser, and in-app updates, while adding Markdown session export, Developer mode, and cleanup of sandbox Low integrity marks.
Installation
Download from DeepSeek GUI official website DeepSeekGUI-Setup-1.2.0.exe. The installer installs according to the current Windows user, and ordinary user rights are sufficient.
- Double-click the installation package.
- After the file installation is complete, the DeepSeek GUI will start automatically.
- The DeepSeek GUI can then be opened from the desktop or start menu.
The distribution package comes with the DeepSeek Harness runtime, Node.js and pnpm are already in it.
First time configuration
On first launch, if you are not signed in and have no API key configured, a welcome screen lets you sign in with a DeepSeek account, add an API key, or set up later. Users who already configured an API key skip the welcome screen.
1. Sign in or enter an API key
To sign in with an account, DeepSeek GUI opens your system browser and returns to the app afterwards; account sessions use the account's credit, so no API key is needed. After sign-in, the official setup introduces your credit, asks what you plan to use it for, and lets you choose how much work detail to show. You can also enter an API key on the welcome screen or in Settings → Models. Harness stores credentials in the DeepSeek GUI data folder; they never go into the installer, the command line, or ordinary diagnostic logs.
2. Select workspace
Return to the homepage and select a project folder as the workspace. Just leave the project where it is, and the Agent will work directly in the workspace you selected.
3. Create or restore a session
Create a new session after selecting the model and workspace. Existing Harness sessions, Profiles, and configurations continue to be managed by the same runtime.
Account and usage
Settings → Account shows the account and the topped-up and granted balances. View usage and Top up open the DeepSeek platform page inside the window, already signed in.
Below it on the same page is DeepSeek GUI's usage view: spending, requests, tokens, and cache hit rate for today, 7 days, and 30 days, plus a 60-day activity heatmap. The data is read with the account sign-in, and the token never reaches any page.
Local Workbench
Inside a conversation, switch between Changes, Git, Project management, and Memory next to Conversation and Trace. These views read local state directly, so refreshing them does not call the model.
- Changes:Group commits, changed files, new files and conflicts to view a single file diff; open it in the right file bar when positioning is required.
- Git：The upper half views the parallel workspace, and the lower half views branches, remotes, leading/behind numbers, and recent commits; commit, push, and PR results will also remain in the current session record.
- Project management:Choose which local skills the sessions in this folder may use.
- Memory:Read or edit the current project's Markdown memory. Experimental Enhanced Memory has been removed.
Git and Pull Request
Dedicated Git tools support viewing status and diffs, staging, unstaged, undoing unstaged changes to tracked files, and creating commits. The remote end, target branch, and commits to be pushed will be displayed before pushing; creating a PR uses the Git and GitHub CLI credentials already in your computer.
Built-in browser and file sidebar
When the assistant opens a public web page, the built-in browser automatically expands to the right of the session. It supports realistic rendering, snapshots, screenshots and interactions; logins, form submissions and other sensitive actions still require user approval.
The browser and the Sidebar on the right side of Harness are displayed alternately. Sidebar provides multi-tab and column preview of code, Markdown, HTML, PDF, and images; it is also accessed when opening files from changes or tool results.
Global memory and project memory
Global memoryLocated in "Settings → Global Memory", it is used to save personal preferences and collaboration requirements across projects. It is edited by the user and is read-only by the assistant.
Project memorysaved in the selected workspace <folder name>.memory.md, used to record project decisions, commitments, and user revisions, maintained by the assistant within the current workspace.
Both memory files provide context at the start of a new session, and the used content is recorded with the session. The assistant can maintain project memory with file tools, or you can edit it in the Memory view. Saving rejects conflicting external changes.
Version 1.2.0 removes experimental Enhanced Memory. On first upgrade launch, valid ordinary entries are appended to the corresponding Markdown files without replacing existing text. Old storage is kept as a backup, including forgotten or unreadable entries. Review your memory files after upgrading.
Local skill library
Settings → Skills imports skills from a folder, a ZIP file, or a single Markdown file. Each import is reviewed first: metadata can be fixed on the spot (only the library copy changes), and blocking issues stop the import.
The Project management tab at the top of a conversation selects the skills each project may use. Sessions in the same folder share one selection, unselected skills are invisible to that project, and the official skills keep working as before.
Session export
Use Export to Markdown in the session menu to save existing records locally, with optional tool calls and reasoning. Export does not call a model. Check conversations, paths, and personal information before sharing.
Developer mode
Settings → General → Developer mode controls additional session logs, plugin lists, and session uploads with feedback. It is off by default. Normal chat requests still go to the chosen model. Enabling it may include previously unreported records and requires confirmation and a Harness restart.
Safety protections
- Protected locations:When an assistant command or file write touches Windows system files, installed programs, or DeepSeek GUI's own code, a red approval card appears, even under Full access. Enter does not approve it, and focus starts on Reject. The check is heuristic, so paths written inside script files are not seen.
- Chat-only workspaces:The user folder, drive roots, and system folders are read-only as workspaces, with Full access and escalation refused.
- Running as administrator:Starting as administrator shows a red warning; if you continue, Full access is disabled.
.gitis read-only by default:In Workspace Write mode, writes to.gitare refused, and staging and unstaging ask for approval first.
Harness and Profiles
Harness manages models, sessions, credentials, permissions, memory, and hooks. The desktop launcher controls the current Harness Home and Profile; v1.2.0 embeds DeepSeek Harness 0.2.0-rc.2.
- Managed Home：By default, DeepSeek GUI's own application data directory is used.
- Existing Home：Advanced users can explicitly select an existing Harness Home; the DeepSeek GUI does not automatically migrate, merge, or rewrite it.
- Profile：Harness profile can be switched; when switching fails, the last-known-good status is retained for recovery.
Terminals and plug-ins
When you need deeper control, you can open the DSH Terminal. DeepSeek GUI prepares private for terminal dsh / node / pnpm Entry without modifying system PATH, registry or shell configuration.
Plugins are managed on the official Plugins page: install, configure, enable, disable, and uninstall them, with a compatibility check against the running Harness version. The plugins bundled with DeepSeek GUI appear under the "Bundled with DeepSeekGUI" group and cannot be removed.
Update in place
Check for updates from the menu or tray. DeepSeek GUI will download the installation package in the background, check the HTTPS address, file size and SHA-256, and display the version and update instructions; the Windows installer will only be launched after user confirmation.
Automatic downloading is on by default and can be turned off in the update panel. Canceling the installation will retain the verified installation package, so there is no need to download it again next time; the file will be checked again before being handed over to the installer.
When GitHub cannot be reached, the same installer is downloaded from the official site instead and goes through the same SHA-256 and size checks.
Data and Offload
By default, the packaged version puts Harness data in %APPDATA%\DeepSeekGUI\dsh, which includes credentials, settings, sessions, Profiles and global memory. The DeepSeek GUI's launcher and window preferences are also saved in its own userData directory; project memory remains in the corresponding workspace.
"Data Location" in the menu can migrate Managed Harness Home. The program is first copied and verified one by one. After switching, Harness is restarted. After the verification is successful again, it will be asked whether to delete the old copy; the Existing Home, project directory and application installation location will not be moved accordingly.
Archived conversations are located in "Settings → Archived Conversations" and can be restored and opened; permanent deletion requires two-step confirmation and will wait for the current reply and tool execution to complete.
Session format remains V4. Older sessions from v1.1.1 or earlier are converted on first open and cannot then be read by v1.1.1.
Uninstalling asks whether to remove app data; upgrades retain sessions, settings, and credentials. Even when app data removal is selected, global memory and global AGENTS.md are retained, and project memory stays in the project folder.
Troubleshooting
Port 3080 is occupied
DeepSeek GUI is currently fixed on the local machine 127.0.0.1:3080 Start the Harness service. When the port is occupied by other programs, an error will be clearly reported instead of secretly changing the port.
Harness startup failed
The packaged version of the diagnostic log is located in the DeepSeek GUI application data directory. Harness service log and bounded rotation deepseekgui-main.log will desensitize common API keys, Bearer tokens and other credential forms; you can export a local diagnostic package from "Settings → BUG Diagnosis and Feedback" or ask the assistant to conduct a redaction triage.
Programs in a project folder will not start
Version 1.2.0 removes sandbox authorization and Low integrity marks after about 30 seconds of workspace inactivity with no sandbox commands running. Clean up old marks under Settings → General → Clean sandbox marks. Busy folders remain authorized; cleanup on large folders can take time.
Why is the window still there after it is closed?
Closing the upper right corner of the window only hides the window, and Harness continues to run in the system tray. To actually stop the runtime, use the tray or menu Quit DeepSeek GUI。
Run from source
The shortest path for developers:
pnpm install
pnpm run build
pnpm run dev:desktopdev:desktop will start the local DSH web service and open the DeepSeek GUI Desktop. More complete architecture and development documentation remains in the GitHub repository.
Licensing and upstream
DeepSeek GUI is an unofficial community product of DeepSeek Harness and is not affiliated with or endorsed by DeepSeek. Harness and the official web UI belong to DeepSeek.
The repository adopts a tiered license: upstream DeepSeek Harness and upstream derivatives continue to remain MIT; the See-Sol-Lab original desktop/product layer adopts PolyForm Perimeter 1.0.1 within the explicit scope. Personal, educational, research, hobby, and permitted internal use are permitted; providing others with alternatives to the DeepSeek GUI requires separate permission.