Introduction¶

In the DSH browser plugin scenario, workspace-like interfaces typically repeatedly feature several types of basic interactions: pane stacking, file trees, tabbed editors, document rendering, and entry points for actions. dsh-ui-workspace turns these capabilities into a set of composable UI primitives. It first addresses the problem of “how to build the interface skeleton,” and then leaves product-specific navigation, data providers, commands, and styles for the consumer to implement.

It is built on top of dsh-ui-container. Below is an introduction to its positioning, capabilities, installation method, and typical usage method.

What is this¶

@ch4acko3/dsh-ui-workspace is a DeepSeek Harness UI plugin maintained by CH4ACKO3, with the package version in the documentation being 0.1.0. Its description is:

Composable workspace primitives for DeepSeek Harness UI plugins

It targets browser plugins, providing composable workspace primitives, and leaves product-specific parts to be implemented by the consumer. Dependencies are intentionally retained: Workspace’s document surfaces call the container’s useUiSurface() at runtime and share its DocumentRef and DocumentSnapshot contracts.

Core Features¶

The capabilities listed below are verified from the README and package information:

Draggable pane stacks
Recursive tree views
Tabbed document editors
Document renderers
Actions
VS Code-style explorer behavior
Client exports can be imported by browser plugins and combined into product-specific pages

The division of labor with dsh-ui-container is as follows:

Container is still an independently installed plugin, possessing a single bundle row that provides the shared uiContainer service.
Workspace consumes this service.
When Workspace is enabled, Container needs to remain installed.

Installation and Enablement¶

First, install Container in the same DSH profile, then install Workspace:

dsh plugin --profile web add github:CH4ACKO3/dsh-ui-container
dsh plugin --profile web add github:CH4ACKO3/dsh-ui-workspace

These commands are profile-scoped and can be executed in any directory.

If installing from Git dependencies, both packages will run prepare builds. When using pnpm 10 or higher, you need to approve the precise package keys reported by the first installation. The approval location is the profile’s pnpm-workspace.yaml, after which you repeat the installation command. Registry releases and packed artifacts do not require this approval.

The environment requirements are as follows:

engines.node: ^22.19.0 || >=24.0.0
packageManager: pnpm@11.19.0

The peerDependencies declaration is as follows:

@ch4acko3/dsh-ui-container ^0.1.0
@deepseek-ai/dsh-client-runtime 0.1.0-rc.6
@deepseek-ai/dsh-client-ui-primitives 0.1.0-rc.6
react ^18.2.0

The dsh.client configuration in package.json is as follows:

{
  "dsh": {
    "client": {
      "immediately": true,
      "platform": "web",
      "inject": [
        "@deepseek-ai/dsh-client-runtime",
        "@deepseek-ai/dsh-client-ui-primitives",
        "@ch4acko3/dsh-ui-container"
      ]
    }
  }
}

Typical Usage¶

After the installation steps above, browser plugin code can reference components from the client exports. The example given in the README is:

import {
  DocumentSurface,
  ExplorerPaneStack,
  TabbedEditor,
  TreeView,
} from '@ch4acko3/dsh-ui-workspace/client'

This package remains importable by browser plugins, used to combine these primitives into product-specific pages.

Use Cases and Considerations¶

Suitable for developers building browser UIs in the DSH web profile, especially scenarios that wish to reuse pane stacks, tree views, tabbed editors, document renderers, actions, and VS Code-style explorer behavior.

Notes before use:

dsh-ui-workspace depends on the shared service provided by dsh-ui-container; when Workspace is enabled, Container needs to remain installed.
Product-specific navigation, data providers, commands, and styles are not implemented by Workspace and need to be implemented by the consumer.
This plugin runs with the current dsh process permissions; before installing, you should check the source code and license.
The documentation does not specify the license type; only LICENSE appears in the files of package.json.
When installing from Git, pay attention to prepare builds and the pnpm approval process.

Conclusion¶

The value of dsh-ui-workspace lies in breaking down common workspace interfaces in browser plugins into composable primitives: panels, trees, editors, renderers, actions, and explorer behaviors can be implemented first, and then product-specific data, commands, navigation, and styles can be filled in by the product side.

GitHub: https://github.com/CH4ACKO3/dsh-ui-workspace. The community directory (standalone site) can be searched by package name; this documentation does not provide a specific directory page URL.

dsh-ui-workspace: Composable workspace primitives for DeepSeek Harness browser extension