AI Agent Hub
Back to plugins
🖥️

dsh-client-open-in-vscode

Client Updated 2026.08.20

Run the following command in DeepSeek Harness:

dsh plugin install quei4r/dsh-client-open-in-vscode

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install quei4r/dsh-client-open-in-vscode in the DeepSeek Harness terminal to install this plugin; the full source is available at https://github.com/quei4r/dsh-client-open-in-vscode .

About this plugin

The DSH web chat is full of file paths — tool-card rows for Write, Edit, and Read, produced-file chips, inline mentions in the prose — yet clicking them typically only copies text, leaving no direct bridge between the conversation and your editor. dsh-client-open-in-vscode closes that gap: it intercepts those clicks and, via a host-side code --goto --reuse-window invocation, opens the file in an already-running VS Code window whose workspace contains the path. This also sidesteps the earlier approach of navigating to the vscode:// protocol, which caused a blank screen inside VS Code webviews.

Beyond opening files, the plugin gives Edit and Write change rows a richer experience: clicking one renders a full-file diff for that specific edit. It reconstructs both versions from the before/after fragments embedded in the row data, first trying the current on-disk file, then the git HEAD version, and hands the result to VS Code's native diff view. When later commits have rewritten the same region, it gracefully falls back to an inline fragment preview. In multi-window setups, routing filters candidates by remote authority, matches the deepest workspace folder containing the absolute path, and brings the correct window to the foreground. Relative paths in the chat are resolved against the session cwd before matching; Alt+click bypasses the interception and triggers the original product behavior.

This plugin is built for developers who work in the DSH web interface and reach for VS Code Desktop to inspect or modify code. On the security side, it reuses DSH's own trust gate at the route level: loopback-only, Sec-Fetch-Site and Origin validation, and path delivery as an execFile argument array that never touches a shell — making drive-by file-open from other sites impossible.

Use Cases

  • Click a file path mentioned by the AI in DSH chat and jump straight to it in VS Code
  • Inspect a full-file diff of a specific edit by clicking the path in a Write or Edit tool card
  • Auto-route to the correct VS Code workspace window and bring it to the foreground in a multi-window setup

Best For

  • Developers who use the DSH web interface for AI-assisted coding day to day
  • Engineers who prefer VS Code Desktop for reviewing and editing AI-generated code
  • Multi-workspace developers who switch frequently between chat and editor