Introduction

The core philosophy of DeepSeek Harness (dsh) is “everything is a plugin”: models, tools, sessions, and interfaces are all replaceable. In practice, many users have to install Node separately, configure profiles, and then add TUI renderers, sidebars, skins, and plugin markets one by one—before the environment is ready, the agent hasn’t even started.

Oh-DSH takes a different approach: it packages DeepSeek Harness, Node.js runtime, local development tools, and a set of built-in plugins into an installable distribution, using a single ohdsh command to switch between Desktop, Web, and TUI. It is maintained by hust-open-atom-club (Huazhong University of Science and Technology OpenAtom Open Source Club), licensed under MIT, and categorized in the community directory under “Client”. As of August 25, 2026, the GitHub repository has approximately 270 stars and 21 forks, with the current release version being 0.1.9.

First, it’s important to clarify: DeepSeek Harness itself is still a developer preview, and its interface may change incompatibly. Oh-DSH is listed in the SkillHub Plugin Directory, but this site is an independent community index and has no official affiliation with DeepSeek or High-Flyer. Do not treat it as an official app store. Oh-DSH is also not a package that uses dsh plugin add to attach to an existing Harness—it is an independent runtime distribution, with its data directory defaulting to ~/.ohdsh, separate from ~/.dsh.

What This Is

In one sentence: Oh-DSH is a client distribution that packages the DSH workbench into an installable application, covering three interaction forms: desktop app, browser, and terminal.

The repository is located at hust-open-atom-club/oh-dsh, with the project homepage at dsh.openatom.club. Model inference can still be directed to the cloud as needed; the Workspace, PTY terminal, Git Review, browser, file browser, session, and plugin state are unified and organized by the local workbench. All three surfaces share sessions, credentials, skins, and plugin caches, while maintaining independent profiles.

The design documentation is straightforward: ohdsh is only responsible for selecting the interaction form, while runtime capabilities continue to be managed by the DSH Profile and Loader—it does not introduce a second plugin system.

Core Features

The capabilities listed below align with the repository README and design documentation (docs/design.zh.md).

  1. Three Interaction Interfaces. Use the same ohdsh command to launch Desktop (Electron), Web (HTTP), or TUI (terminal). The full version includes all three; you can also install Web-only or TUI-only, omitting Electron as needed.

  2. Local Development Workbench. Built-in Workspace, PTY terminal, browser, file browser, Side chat, and Trajectory; panels can be collapsed, pinned, split-screened, or fullscreened. Desktop sidebar capabilities track upstream DSH-better-sidebar, TUI rendering tracks dsh-TUI, and Oh-DSH provides a unified launcher, layout, themes, and distribution packaging on top.

  3. Git Review. View workspace changes and commit diffs, add review comments on code lines, and complete branch, commit, and push operations within the same sidebar.

  4. Plugin Market. Desktop, Web, and TUI can all search, preview, and install plugins, sharing a unified installation transaction and recovery state. The directory indicates which interfaces each plugin actually affects—some plugins only work on Web or Desktop, not TUI, and this is clearly distinguished in the interface.

  5. Cross-Platform Skins. @oh-dsh/skins provides a unified theme ID for all three platforms, adapting to Web/Desktop CSS and TUI color palettes respectively.

  6. Built-in Vision Tools. @oh-dsh/vision provides the same view_image tool across all three platforms, enabling OCR, image reading, and interface diagnostics for local images within the Workspace, HTTP(S) images, or image data URLs; credentials can be configured in “Settings → Plugins → Vision”.

  7. Self-Contained Runtime. Each distribution bundles a fixed version of DSH and Node, requiring no pre-installed runtime environment. The installer validates the SHA-256 checksum of the release before modifying an old installation; if the download fails or the checksum doesn’t match, the original installation remains usable.

Installation and Activation

Oh-DSH’s installation entry points are install.sh (Linux / macOS) and install.ps1 (Windows) in the repository root—not dsh plugin add. Both the SkillHub directory page and GitHub README point to this installer.

For Linux and macOS, the default installation installs the TUI and registers ohdsh to ~/.local/bin:

curl -fsSL \
  https://raw.githubusercontent.com/hust-open-atom-club/oh-dsh/main/install.sh \
  | bash

When Web or Desktop is needed, explicitly specify the surface:

curl -fsSL \
  https://raw.githubusercontent.com/hust-open-atom-club/oh-dsh/main/install.sh \
  | bash -s -- --surface web

curl -fsSL \
  https://raw.githubusercontent.com/hust-open-atom-club/oh-dsh/main/install.sh \
  | bash -s -- --surface desktop

Windows (PowerShell 5.1+, also installs TUI by default):

irm https://raw.githubusercontent.com/hust-open-atom-club/oh-dsh/main/install.ps1 | iex

Executing remote scripts via piping runs external code on your machine. Before installation, you should check the source repository and the MIT license. For reproducible installations, use --version to pin the release tag, such as --version v0.1.9.

You can also manually download from GitHub Releases: the full version includes Desktop + Web + TUI; Web-only excludes Electron; TUI-only has the smallest footprint, suitable for SSH and pure terminal environments. On macOS, drag the DMG to Applications; on Linux, run the AppImage or apt install the deb; on Windows, run the NSIS installer.

After installation, open a new terminal (or a new PowerShell on Windows) and use the unified command to launch the installed interface:

ohdsh tui              # Terminal interface
ohdsh web              # Web interface
ohdsh web --port 3080  # Specify Web port
ohdsh desktop          # Desktop application (gui is an alias)

ohdsh will only launch installed surfaces; repeated installation with the same version is a no-op. Add --force to force reinstallation, or --uninstall to uninstall by surface. Web and TUI can be installed in parallel, and the shared ohdsh launcher routes subcommands to the corresponding payloads.

Typical Usage

All three platforms default to sharing ~/.ohdsh to store cache, configuration, sessions, credentials, and plugin state. To change the data directory, set the environment variable OH_DSH_HOME:

export OH_DSH_HOME=/tmp/my-ohdsh
ohdsh web

The most common daily development paths are:

  1. Install the full version or Desktop surface, run ohdsh desktop, and open Workspace, terminal, and Git Review in the graphical interface.

  2. For servers or lightweight environments, install only Web-only, run ohdsh web --port 3080, and access the printed address in a browser.

  3. For SSH remote access, install only TUI-only, run ohdsh tui; add --fullscreen when alternate screen is needed.

  4. In any surface’s plugin market, search, preview, and install community plugins; installation transactions support isolated previews and risk confirmations, following the same process as the human UI.

  5. To upgrade packaged web/tui distributions: ohdsh update (or ohdsh update web / ohdsh update tui), which re-runs the installer’s verification and atomic replacement. Desktop checks for releases via its built-in updater.

The built-in Agent preset includes a liangshen (Liang Shen mode): it maintains Minimal dual tools in the first round, then opens the full tool catalog after the first tool call. Web/Desktop select it in the settings page; TUI uses /preset liangshen.

Running the development version from source requires Node.js, pnpm, and platform build tools. The README includes steps like git submodule update --init --recursive, pnpm run build:dsh, and make tui; regular users can just use the installer.

Applicable Scenarios and Notes

Suitable for:

  1. Those who want to quickly obtain the complete DSH workbench without assembling Node, profiles, and a bunch of UI plugins themselves.

  2. Developers who need to switch between desktop, browser, and terminal while sharing session and plugin state as much as possible.

  3. Those who value the integrated experience of Git Review, sidebar files/terminal, and plugin market, and are willing to use Oh-DSH’s packaged upstream combinations (better-sidebar, dsh-TUI, vision, etc.).

  4. Scenarios where servers or CI only want to run Web/TUI without Electron—you can install only the corresponding surface.

Before use, note the following boundaries:

  1. Independent Data Directory. Oh-DSH defaults to ~/.ohdsh, not ~/.dsh. For users with existing Harness installations, plugins and profiles will not migrate automatically. To load other plugins in Oh-DSH Desktop, point DSH_HOME to the corresponding profile under ~/.ohdsh as per each plugin’s README.

  2. Plugins Run with Current Process Permissions. The installer downloads and extracts release assets, and plugin market installations also execute code. Check the source code and MIT license before installation; pin versions when possible.

  3. Only Installed Surfaces Are Supported. If Desktop isn’t installed, ohdsh desktop won’t magically appear—you must first run the installer with --surface desktop or download the full release.

  4. Platform Support. Officially supported on macOS, Linux, Windows (x64; macOS also supports arm64). Linux Desktop uses AppImage or deb; on macOS, unnotarized builds may require right-clicking “Open” in Finder the first time.

  5. DeepSeek Harness Is Still in Preview. Oh-DSH bundles a fixed version of DSH; upgrading Oh-DSH does not equate to upgrading the dsh CLI in your system—they can coexist, and data directories are separate.

  6. Community Directory Is for Reference Only. SkillHub and GitHub stars may fluctuate; refer to the repository README and release page.

Summary

Oh-DSH transforms DeepSeek Harness from “assembling the environment yourself” to “download and use”: a single ohdsh command switches between Desktop, Web, and TUI, with a built-in Node runtime, workbench, Git Review, plugin market, and cross-platform skins. It is an MIT-licensed open-source client distribution maintained by hust-open-atom-club, not an official DeepSeek product, nor a regular plugin added via plugin add to an existing dsh.

Directory page: https://www.skillhub.cn/plugins/hust-open-atom-club/oh-dsh

GitHub: https://github.com/hust-open-atom-club/oh-dsh