dsh-win-toolkit

1. 安装并启动 DeepSeek Harness：npx @deepseek-ai/dsh web
2. 在终端执行上面的安装命令（CLI 会解析插件并核验来源）
3. 用 dsh plugins list 确认已安装，必要时重启 Harness 生效

插件以当前 dsh 进程的权限运行，安装时可能执行代码。请先通读仓库源码与许可证，确认无破坏性命令与越权访问；本站只做索引，不对第三方插件安全性作担保。

事实信息来自公开插件目录快照（2026-10-03），介绍文案由本站再加工。

以下为插件仓库 README 全文（原始内容，由公开目录抓取整理）。

# dsh-win-toolkit

![dsh-win-toolkit](https://raw.githubusercontent.com/Edge-Echo/dsh-win-toolkit/main/banner.svg)

[![npm version](https://img.shields.io/npm/v/dsh-win-toolkit?color=0078d4&logo=npm)](https://www.npmjs.com/package/dsh-win-toolkit)
[![npm downloads](https://img.shields.io/npm/dm/dsh-win-toolkit?color=6366f1)](https://www.npmjs.com/package/dsh-win-toolkit)
[![license](https://img.shields.io/npm/l/dsh-win-toolkit?color=0078d4)](LICENSE)
[![GitHub stars](https://img.shields.io/github/stars/Edge-Echo/dsh-win-toolkit?color=6366f1)](https://github.com/Edge-Echo/dsh-win-toolkit)

**Windows-native capability pack for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (dsh).**

Gives your dsh agent real Windows superpowers — clipboard, system notifications, hosts file inspection, and network diagnostics — backed by safe, parameterized PowerShell. No extra installs, no admin rights required for the current toolset.

> 中文文档见 [README.zh.md](README.zh.md)。

## Tools

| Tool | What it does |
|---|---|
| `win_clipboard_read` | Read the current clipboard text |
| `win_clipboard_write` | Write text to the clipboard |
| `win_notify` | Show a system popup notification (auto-closes) |
| `win_hosts_list` | Read the Windows hosts file |
| `win_netdiag` | DNS resolution + TCP port test for any host |

## Install

```sh
dsh plugin --profile web add dsh-win-toolkit
dsh web   # restart
```

Then just ask your agent, e.g.:
- "check if github.com:443 is reachable" → `win_netdiag`
- "put this text on my clipboard" → `win_clipboard_write`
- "notify me when you're done" → `win_notify`

## How it works

Every tool runs a short PowerShell snippet through `powershell.exe -NoProfile -NonInteractive`. All user input crosses the script boundary as **Base64** — never string-interpolated — so argument injection is structurally impossible.

- Config: `psTimeoutMs` (default 20000) — per-call PowerShell timeout, settable in your profile's `cordis.patch.yml` under the `win-toolkit` entry.
- Windows-only: tools fail loudly with a clear error on non-Windows platforms (the entry itself is a no-op there).

## Roadmap

- `win_hosts_edit` (admin-gated hosts entries), `win_env`, `win_service`, `win_window`, `win_task`, `win_netdiag` deep mode (proxy check, DNS server, traceroute).

## Troubleshooting

- Tools fail with "PowerShell failed": usually an anti-virus or execution-policy quirk — the plugin uses `-NoProfile -NonInteractive` but policy still applies. Check `Get-ExecutionPolicy`; the plugin does not require RemoteSigned.
- Want to see exactly what runs? The PowerShell snippets are short and readable in `src/index.ts`.

## Links

- npm:
- GitHub:
- License: MIT