dsh-workbench-ecs: Control Alibaba Cloud ECS Instances with a DSH plugin

What Does It Do?

It is a DSH plugin for DeepSeek Harness that lets the Agent control remote Alibaba Cloud ECS instances through the local Workbench CLI. It solves the usual friction of remote ops: instances without public IPs are unreachable, long commands block the session, and destructive commands run unchecked. The plugin routes access through the Workbench backend channel and ships nine agent-native tools plus a visual settings panel. It is maintained by nishuoyang under the MIT license, last updated in 2026-09.

Core Features

• Nine agent-native tools: listing, diagnosing, executing, uploading, downloading, deploying, runbooks and sessions, covering the full list → diagnose → execute → upload → restart → verify loop.
• Detached long tasks with a log cursor: a job can start in the background with remote nohup, immediately returning a job id and log path, while the plugin polls increments so other calls on the same instance interleave normally.
• Pseudo-sessions: passing a session id keeps the working directory and environment across calls, different ids stay isolated, and an idle session resets after a timeout with an explicit notice.
• Visual settings panel: CLI status, an instance browser with search and auto-refresh, one-click diagnostics with disk and memory gauges, a guarded publish wizard with templates, session management and an operation timeline, adapting to light and dark themes.
• Safety guard: destructive commands request confirmation through the Harness approval service and are rejected unless explicitly allowed; a read-only mode blocks write operations before they reach a shell.
• Transfer integrity: uploads can verify local and remote digests, deployment enables this by default and aborts before restart on a mismatch.

How to Use This Plugin?

After enabling it in DSH, simply ask the Agent to act on a target instance, such as listing instances, reading logs, uploading a file or running a diagnostic script. Long-running commands can be handed to background jobs and their output read incrementally by byte cursor; specify a session id when context must persist across calls. For releases, prefer the guarded wizard in the settings panel, and deliver scripts as base64 to a remote file so Chinese text, quotes and multi-line bodies need no escaping.

How to Troubleshoot This Plugin?

When a tool reports a CLI-level error, the plugin renders the returned code and message into a readable notice, so first check whether the local Workbench CLI is available and the instance reachable. If upload or deploy verification fails, the local and remote digests differ, so retransfer the file as described in the official documentation. A rejected command usually comes from the safety guard or read-only mode; confirm the write is genuinely needed, then adjust the allow settings as documented.