dsh-win-toolkit

Let your agent use Windows itself: read the clipboard, raise a notification, inspect the hosts file, test whether a port is open.

When you need this

• You copied something and want the agent to read it directly, instead of pasting it into the chat
• A long task finishes while you are in another window and you want a desktop notification
• GitHub is unreachable and you want the agent to diagnose it rather than guess

Every value crosses the PowerShell boundary as Base64, so clipboard contents and hostnames cannot inject a command. doctor checks the environment before you run into a missing piece.

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。

Feedback

Installs are visible in the download counts; whether this helps is not. If you use it, one line about the actual task is worth more than a star — particularly if it did not work, which is the case that never gets reported:

• what you were trying to do
• whether it did it
• what was missing or wrong

Tell me in an issue — or if something is already broken, just open a normal bug report.

Check your environment first

dsh-win-toolkit doctor

It verifies the platform, PowerShell, execution policy, clipboard access, WScript.Shell COM and hosts readability — everything the tools rely on.

Requirements

Run dsh-win-toolkit doctor to verify all of the above on your machine before blaming the plugin.

Tools

Install

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: https://www.npmjs.com/package/dsh-win-toolkit
• GitHub: https://github.com/Edge-Echo/dsh-win-toolkit
• License: MIT

Related

Part of the dsh-toolkit family — small, independently useful pieces for DeepSeek Harness:

• dsh-mcp-bridge — install six curated MCP servers, verified in CI
• dsh-win-toolkit — clipboard, notifications, hosts, port checks on Windows
• dsh-netassist — network and proxy diagnosis with a concrete next step
• dsh-driftwatch — behaviour-drift reports between two session logs
• dsh-ledger — what the agent did to your files, provably unaltered
• dsh-release-evidence — one verifiable artifact per release
• mcp-netassist — the same network checks as an MCP server, any client