Relay Plugins for DeepSeek Harness

August 30, 2026 · View on GitHub

English | 中文

Discover and manage plugins from a conversation, or add Codex, Claude Code, workspace files, and an interactive terminal to the official DeepSeek Harness. No DSH fork or core patch is required.

Codex conversation and workspace files running in official DSH

The screenshot shows a live Codex App Server reply beside the Files view on a clean official DSH 0.1.1-rc.2 profile. The same real run, from an actual npm installation, also verified a live Claude Agent SDK reply and a Terminal command in the Relay workspace.

Watch Plugin Manager install Codex in 40 seconds · Open the full-size live screenshot · Read the recording and compatibility evidence

Choose What You Need

GoalInstallNotes
Find, install, update, or remove DSH plugins through Chatrelay-dsh-plugin-managerSearches npm and GitHub; every mutation requires separate confirmation, and Settings remains read-only help.
Start Codex conversations in DSHrelay-dsh-plugin-codexIndependent backend powered by Codex App Server.
Start Claude Code conversations in DSHrelay-dsh-plugin-claudeIndependent backend powered by Claude Agent SDK.
Browse workspace filesrelay-dsh-plugin-workbench + relay-dsh-plugin-filesFiles uses the shared Workbench side-panel host.
Open a terminal panelWorkbench + relay-dsh-plugin-terminalAdd Codex or another provider for a live shell.
Build another side or bottom viewWorkbenchUse its public contracts instead of importing another feature plugin.

Plugin Manager, Codex, and Claude do not depend on the Relay runtime or Workbench. Files and Terminal depend only on Workbench's public plugin contract. Relay Events is a separate optional runtime and is not required by these plugins.

Install the conversation-first manager by itself, restart DSH once, then use /plugins or an ordinary natural-language request:

dsh plugin --profile web add --save-exact relay-dsh-plugin-manager@0.1.0-rc.2
/plugins find a plugin for Feishu
list installed plugins and whether DSH needs a restart

Install From npm

The backend plugins currently recommend their tested release candidates while DSH remains in preview. The Workbench plugins use their stable releases.

pnpm dlx @deepseek-ai/dsh@0.1.1-rc.2 plugin --profile web add \
  relay-dsh-plugin-manager@latest \
  relay-dsh-plugin-codex@next \
  relay-dsh-plugin-claude@next \
  relay-dsh-plugin-workbench@latest \
  relay-dsh-plugin-files@latest \
  relay-dsh-plugin-terminal@latest

pnpm dlx @deepseek-ai/dsh@0.1.1-rc.2 web

Install only the rows you need. Files and Terminal must list Workbench in the same command because DSH profiles intentionally reject GitHub packages hidden as transitive dependencies. A live terminal also needs a provider; Codex is the currently published provider in this suite.

KeySync's one-click DSH setup already installs Plugin Manager. Do not add it a second time there; the npm command is for standalone official DSH Profiles.

Install From GitHub

Use GitHub installs to test the newest unreleased code. Pin a tag or commit SHA for reproducible environments instead of leaving #main in production.

pnpm dlx @deepseek-ai/dsh@0.1.1-rc.2 plugin --profile web add \
  github:yangbobo2021/relay-dsh-plugin-manager#main \
  github:yangbobo2021/relay-dsh-plugin-codex#main \
  github:yangbobo2021/relay-dsh-plugin-claude#main \
  github:yangbobo2021/relay-dsh-plugin-workbench#main \
  github:yangbobo2021/relay-dsh-plugin-files#main \
  github:yangbobo2021/relay-dsh-plugin-terminal#main

Restart DSH Web after installing, updating, or removing plugins.

Verify the Installation

dsh plugin --profile web why relay-dsh-plugin-codex
dsh plugin --profile web why relay-dsh-plugin-claude
dsh plugin --profile web why relay-dsh-plugin-files
dsh plugin --profile web why relay-dsh-plugin-terminal
dsh plugin --profile web why relay-dsh-plugin-manager

Then open a new DSH session. Ask to list installed plugins, or open Settings > Plugins > Plugin marketplace for concise usage help. Codex and Claude Code should appear in the mode menu. With a workspace selected, the Workbench menu should expose Files and Terminal.

The five backend/workbench repositories include English and Chinese setup; all six repositories document verification, npm publishing, and a GitHub development path. See the longer article, No Fork Required: Add Codex, Claude Code, Files, and Terminal to DSH, for the design rationale and a guided walkthrough.

The Codex plugin also treats App Server reliability as a product contract: its Settings status distinguishes startup, connection, runtime availability, and rebind failures; blank-session model selection follows the chosen backend; normal forks use App Server thread/fork; and invalid fork provenance or stale approvals fail closed without silently creating a replacement Codex Thread.

For the working model rather than package structure, read the Turning DSH into a Multi-Agent Project Workbench series: it starts with task choice across native DSH, Codex, and Claude, then covers App Server, Claude Sessions, the project Workbench, and the boundary for future coordination.

For the complete multi-device run, read Leave the Work PC Running: KeySync installs official DSH with Plugin Manager built in; the optional plugins add the three conversation choices, Files, and Terminal, and another device reopens the original session.