DSH Codex Desktop is a community-maintained desktop distribution of DeepSeek Harness. It is not an official DeepSeek AI product.

DSH Codex Desktop turns DeepSeek Harness into a native, ready-to-run desktop workbench. The installer includes the required Node.js runtime and local DSH runtime: install it, open it, then start working. You do not need to prepare a Node.js environment or launch DSH from a terminal.

Download and start

Get the current installer from GitHub Releases.

1. Download the package for your platform.
2. Install and open DSH Codex Desktop.
3. Wait for the built-in local DSH service to finish starting.
4. Create a task, select a model and permission mode, then work in your project.

The application keeps DSH data in your existing user profile (%USERPROFILE%\.dsh on Windows), so sessions and settings remain available after application upgrades.

A complete desktop workbench

Product preview

Explore the desktop workspace, light-theme settings, and plugin management pages. The home screen and 11 settings and plugin screenshots come from the newly supplied desktop captures; the conversation, context, and sidebar previews are retained from earlier captures. Plugin versions, counts, and states reflect each capture. Click any image to view it at its original resolution.

Home: project navigation, task entry points, and composer.

Conversation: messages, trajectory, context, and task input.

Included on first launch

The installer ships with the local runtime required to start DSH. On first launch, it prepares the desktop-facing community plugins in the Web profile:

You can later manage additional plugins from the plugin market. The desktop application keeps its own runtime separate from profile-installed community plugins so plugin changes do not overwrite the application runtime.

The desktop bridge ships with the app and is injected only when Desktop starts DSH; it does not need to be installed in the shared Web profile. Running dsh web manually uses Web's own plugin management path. Desktop migrates and backs up bridge configuration left by older versions on startup.

DSH product ecosystem

For a desktop workbench, download DSH Codex Desktop. Existing DeepSeek Harness installations can add plugins as needed by following each project's README. Below are 11 first-party plugins; consult the corresponding desktop release notes and bundled catalog for what that version includes.

The desktop app also integrates DSH Better Sidebar and App Market as third-party plugins for file navigation and plugin discovery and installation.

Updates and recovery

• Desktop updates for the installer are checked after startup by default and notify you when a new release is available. Settings → Updates can instead download releases automatically or switch to manual-only checks. Installation and restart always require an explicit action. A zip build only checks for a new version and does not download the installer; download the new zip from Releases, quit, and replace the current folder.
• DSH reload is available from the tray menu after changing plugins or profile configuration; it restarts the local DSH service without reinstalling the desktop application.
• Plugin updates remain in the DSH settings and plugin market. A failed plugin installation is not activated as a running bundle.
• Startup recovery removes stale community-plugin registrations that no longer have an installed package, then retries the local DSH startup.

System requirements

Privacy and security

• DSH configuration, sessions, and credentials remain in the current user's DSH directory. Uninstalling the desktop app does not delete them.
• The launcher accepts only validated 127.0.0.1 local HTTP addresses for its embedded window.
• External HTTP(S) links open in the system browser. File, JavaScript, and data URLs are blocked.
• Electron uses context isolation and sandboxing, with Node.js integration disabled for the DSH page.
• Your configured model providers and DSH tools may make their own network requests. Review their settings and privacy policies before use.

Development

The Windows packaging job also runs pnpm smoke:upgrade <old-exe> <new-exe> before uploading artifacts. This regression check requires the Windows x64 executable from Desktop 1.0.51 (archive plugin 0.1.34) and the current build executable, each with its complete resources directory. It launches both versions offline in an isolated profile and checks plugin versions, the original store, and preserved user configuration. It is separate from pnpm test because it requires both packaged applications.

Bundled Code Review and PUA

Code Review and PUA are included in the bundled plugin catalog. PUA defaults to globally off when no saved choice exists. Enable it in Settings → Plugins → PUA Configuration; saved choices are preserved on later launches. The plugin remains loaded so its settings are available.

Bundled pet integration

The bundled @michengai/dsh-codex-pet 0.1.13 is distributed offline and installed automatically on first launch. Select a pet and enable visibility in pet settings to use the native companion. The plugin exposes window.dshPet API version 1. Desktop subscribes to snapshots and forwards conversation actions through that API; Desktop owns rendering, dragging, position storage, click-through, v2 idle gaze and window recovery. The plugin remains usable in a web browser without Desktop. Older plugins exposing only dshDesktopPet are not supported by this adapter.

Run npm run smoke:pet to build and verify real Electron windows, preload/IPC, multi-session approval and answers, stale-command rejection, reload, hide and display handoff. The test uses a protocol fixture and a tiny image fixture, requires only this repository's development dependencies, and cleans its temporary user directory. It does not replace an installed-plugin or packaged-release acceptance test.

Development requires Windows, Node.js 24.21.0, and pnpm 11.26.0.

[Console]::OutputEncoding = [System.Text.Encoding]::UTF8
$OutputEncoding = [System.Text.Encoding]::UTF8
pnpm install --frozen-lockfile
pnpm test
pnpm run dist

Local build artifacts are written to release\ and are not committed. Pushing a vX.Y.Z tag starts the packaging workflow for Windows x64, macOS arm64/x64, and Linux x64/arm64 AppImage / deb artifacts.

License

This project is licensed under Apache License 2.0.