Introduction

Running agent tasks in DeepSeek Harness (DSH) often incurs costs in two areas: the tokens from tool returns stuffed into the context, and the extra rounds the model takes between errors and retries. While the official tools cover a wide range, tasks can slow down and bills can balloon when return bodies are too large or formats are unfavorable for the model to continue coding—especially when reading large files, batch modifying repositories, or operating under Native / PTC harness modes.

Below is an introduction to the community plugin dsh-ops (npm package name dsh-ops, repository T-Auto/dsh-ops). Its explicit goal is to improve token efficiency: it replaces or hides certain official tools with a new series of ops tools and utilizes DSH’s reserved tools_addition for progressive loading, thereby reducing prompt inflation and call counts in common scenarios. It is maintained by the T-Auto team and categorized as a “Model Inference” related plugin in community directories like SkillHub. As of the record, it has approximately 3665 stars and 101 forks on GitHub (subject to real-time data on the repository page).

What is this

dsh-ops is a low-level operations tool plugin for DSH, self-described as having a low modification surface, low invasiveness, and maximal compatibility with other plugins. It does not start a separate harness but mounts components within the existing DSH process, packing capabilities such as files, Shell, PTC, and optional TUI sidebars into your desktop, web, or dsh-TUI applications by profile.

The current release source is distributed under the MIT license (version 0.4.1 recorded in package.json). The plugin runs with the permissions of the current DSH process; before installation, you should verify the source code and License / Provenance on GitHub.

Core Features

Trade-offs between ops tools and official tools

The plugin performs most read/write and command operations via tools in the ops namespace and can hide certain official tools at the policy layer, reducing the model’s back-and-forth exploration between functionally overlapping tools. The design emphasizes “solution-level” replacement rather than a wholesale rewrite of DSH, facilitating coexistence with other community plugins.

Progressive tools_addition

It enables DSH’s reserved tools_addition dynamic tool loading, placing heavy scenarios like PDF/Word reading and large-scale file modifications into on-demand advanced capabilities. Common conversations do not stuff the schemas of these tools into the system prompt all at once, thereby controlling tokens; they are loaded only when needed to avoid long-term prompt inflation.

Native Mode

Provides a more compact return surface with line numbers and clearer error messages for the Native harness, aiming to curb the “error—blind retry” loop and reduce invalid rounds.

PTC Mode

Provides tools that return structured JSON for PTC (Programmatic Tool Calling) mode, reducing the total token count and mental burden for the model when writing TypeScript under PTC. The repository states that the PTC SDK directory contains 18 APIs: 15 are file/document tools, plus interfaces for batch processing, result references, and loaders. See PTC Design and Usage in the repository for details.

Shell Behavior on Windows

Windows platform only: You can enable ops_bash consistent with DSH’s native bash behavior and optionally disable PowerShell, making Shell task paths more consistent with the Linux/macOS experience. See PROVENANCE in the repository for license and upstream component details regarding the optional payload @dsh-ops/bash-win32-x64.

dsh-TUI Optional Read-only Sidebar

After enabling the dsh-ops/tui plugin line in dsh-TUI and restarting, you can add an OPS read-only sidebar: it does not steal focus or trigger extra tool calls, and is used for browsing bounded retained metadata. When focused, it supports local shortcuts such as f for filtering, n/p for paging, and a for confirming cross-session reminders. See Sidebar Documentation for instructions.

Removed Background Components

Earlier versions included the FastCtx background task (dsh-ops/background); this component has been removed after 0.3.2. If your profile still retains the background line, loading will only log a warning and not publish tools; you can simply remove this line from the configuration. Files provisioned by the old version under <DSH_HOME>/dsh-ops/ need to be cleaned up separately according to the README.

Installation and Activation

There are two installation methods: DSH Plugin Market (npm package name) and npm one-click installation / Official CLI. Please do not use the dsh plugin add github:owner/repo form which does not appear in the documentation.

Plugin Market

  1. Search for the npm package name dsh-ops in the plugin market of your target DSH application.
  2. Select “Custom Address” and fill in the Huawei Cloud npm mirror (currently recommended in the documentation due to known issues with npmmirror):
https://mirrors.huaweicloud.com/repository/npm/
  1. Enable the plugin in the application after installation. If you can stably access the official npm source, you may also select the official source.

npm One-click Installation

You must initialize the target DSH application first and explicitly select a profile. tui corresponds to the dsh-tui profile of the dsh-TUI product, not the old tui directory name.

For the desktop端, use the CLI bundled with the desktop application; the default detection path on Windows is %LOCALAPPDATA%\Programs\DeepSeek Harness\resources\runtime\cli\bin\dsh.cmd. If the installation directory is different, use --dsh-cli to point to that dsh.cmd.

To preview the installation (without modifying the profile), add --dry-run:

npx --yes dsh-ops@latest install --profile desktop
npx --yes dsh-ops@latest install --profile web
npx --yes dsh-ops@latest install --profile tui

You can also use the official CLI directly (note that the desktop profile can only be managed by the desktop’s bundled entry; the standard dsh CLI cannot manage the reserved desktop profile):

dsh plugin --profile web add dsh-ops
dsh plugin --profile dsh-tui add dsh-ops
"<桌面安装目录>\resources\runtime\cli\bin\dsh.cmd" plugin --profile desktop add dsh-ops

Update, Status, and Uninstall

Update: Re-run the same npx ... install --profile ... command, or dsh plugin ... add dsh-ops@latest, and reload or restart as prompted by the application.

Check status / Uninstall (replace desktop with web or tui):

npx --yes dsh-ops@latest status --profile desktop
npx --yes dsh-ops@latest uninstall --profile desktop

You can also uninstall via the plugin market or use dsh plugin --profile ... remove dsh-ops. The separately provisioned Bash runtime can be removed with dsh-ops bash-runtime remove --yes. To clean up remnants from the old <DSH_HOME>/dsh-ops/, use npx --yes dsh-ops@latest uninstall --yes; ~/.fastctx/ is not deleted by default, add --purge-fastctx if needed.

Typical Usage and Documentation Entry

After installation and activation, ops tools will appear in the list of callable tools for the model during the DSH session; specific tool names, arguments, and policies (e.g., which official tools to hide) are subject to the repository’s Usage Guide, Component Reference, and Configuration Reference.

For PTC integration and Native behavior differences, see native-ptc.md. For troubleshooting and acceptance, refer to FAQ and Manual Acceptance.

The README includes a token efficiency comparison chart from the team’s internal benchmarks; for the complete benchmark, please refer to subsequent updates in the repository. This article does not restate unpublished figures.

Applicable Scenarios and Notes

Better suited for: Developers who frequently perform repository-level read/write, Shell, document processing, or PTC script generation in DSH; those who want to reduce tokens and rounds without significantly changing their workflow; users needing Shell behavior aligned with native bash on Windows; and users of dsh-TUI who want a read-only OPS metadata sidebar.

Points to note:

  1. The plugin runs with the same permissions as DSH. Before operations involving file deletion, Shell commands, or batch modifications, you should understand the policies and tool scope.
  2. Policies related to hiding official tools may affect your or other plugins’ dependence on built-in tools; it is recommended to check the CHANGELOG after upgrading dsh-ops or DSH.
  3. Community directories (like the SkillHub Plugin Page) are independent of DeepSeek / High-Flyer and are not official app stores; installation sources should conform to the npm package and mirrors written in the README.
  4. Supported platforms (package.json): win32 / linux / darwin, x64 / arm64.

Conclusion

dsh-ops makes “fewer tokens, fewer rounds” an installable DSH plugin: the ops tool surface, tools_addition progressive loading, Native / PTC dual-mode optimization, and the optional TUI sidebar are all delivered via the same npm package dsh-ops based on profiles. To browse the brief and category, open the community directory dsh-ops; for source code, installation details, and roadmap, see GitHub T-Auto/dsh-ops.