Preface

When developing DSH plugins or Agents, a common issue isn’t the lack of individual capabilities but rather fragmented context: the session is in one place, the terminal in another window, and file changes and Git updates require constant switching.

DSH Studio aims to integrate sessions, local terminals, file browsing, Git Review, and plugin states into a single project workspace. Designed for DeepSeek Harness, it offers both Desktop and Web entry points, making it suitable for scenarios where local development tools need centralized management.

What is This

The repository identifier for DSH Studio is euanguo/dsh-studio, categorized as a client application, and licensed under the MIT License.

Its one-sentence positioning is: a local development workbench for DeepSeek Harness. It primarily addresses the challenge of separately handling multiple projects, sessions, local terminals, file browsing, Git Review, and plugin installation management.

Core Features

Multi-Project Workspace

DSH Studio organizes work context using a three-tier structure: Project -> Worktree -> Session. Projects support grouping and aliases, and can automatically detect project icons.

Integrated Tool Area

The project-level tool area includes project-level PTY, file browsing and preview, browsers, and Subagents. These capabilities are placed within the same workbench, reducing the need to switch between multiple windows.

Git Review

Git Review supports staged, unstaged, and untracked partitions, commit history, commit file trees, and line-level review targets.

Smart Commit

DSH Studio offers smart commit: one-click generation of commit messages based on current changes, with configurable models and thinking intensity.

Note that the documentation mentions Source Control AI is under development and is not yet a stable release commitment.

Desktop + Web Homogeneity

Desktop and Web use the same runtime, Profile, plugins, and data boundaries. This means that the plugins and data models seen in both entry points are consistent.

Plugin Marketplace

The plugin marketplace supports browsing and installing plugins from multiple sources, and provides candidate preview, approval, source locking, and recovery processes.

Installation and Enablement

First, decide whether to use Desktop or Web. The documentation mentions that the installed Desktop and Web by default share ~/.dsh-studio to store cache, configuration, sessions, credentials, and plugin states.

If using the Web-only package, it can be run directly after extraction:

./bin/dsh-studio web

The Web UI listens by default on:

http://127.0.0.1:3080

To specify a port:

dsh-studio web --port 3080

The macOS full version allows adding the in-app launcher to PATH. The optional command provided in the documentation is:

sudo ln -sf \
  "/Applications/DSH Studio.app/Contents/Resources/bin/dsh-studio" \
  /usr/local/bin/dsh-studio

This command comes from the “Unified Installation Command (Optional)” section in the documentation, which does not state it is the only installation method.

To unify and change the data directory, you can set:

export DSH_STUDIO_HOME=/path/to/dsh-studio-home

To switch the default root directory, use --channel stable or --channel dev:

dsh-studio desktop --channel stable
dsh-studio web --channel dev

Environment variables can also be used:

export DSH_STUDIO_CHANNEL=stable
export DSH_STUDIO_CHANNEL=dev

Typical Usage

Below are the executable entry points provided in the documentation:

  1. Launch DSH Studio Desktop:
dsh-studio desktop
  1. Use Desktop with a launch alias:
dsh-studio gui
  1. Launch DSH Studio Web:
dsh-studio web
  1. Specify the Web port:
dsh-studio web --port 3080
  1. Switch data directory and launch:
DSH_STUDIO_HOME=/tmp/dsh-studio-home dsh-studio web

Suitable Scenarios and Notes

Suitable for:

  • Local development workflows that need to manage Project, Worktree, and Session within the same workspace.
  • Developers who need to centrally manage project-level PTY, file browsing, Git Review, and plugin states.
  • Teams that need Desktop and Web entry points to share the same runtime, Profile, plugins, and data boundaries.

Notes:

  • DSH plugins run with the permissions of the current DSH process; check the source code and license before installation.
  • Source Control AI is an experimental feature mentioned in the documentation, currently under development and not yet a stable release commitment.
  • Desktop and Web by default share ~/.dsh-studio to store cache, configuration, sessions, credentials, and plugin states.
  • The documentation mentions that complete third-party licenses, fixed versions, and adaptation boundaries can be found in THIRD_PARTY_NO related notes. However, the current documentation is incomplete, so the complete filename and terms cannot be confirmed. It is recommended to refer to the official files in the repository.

Links

The value of DSH Studio lies in bringing DSH sessions, local tools, Git changes, and plugin management into a locally organized workbench. The directory page and repository links are as follows:

  • Directory Page: https://www.skillhub.cn/plugins/euanguo/dsh-studio
  • GitHub: https://github.com/euanguo/dsh-studio