A Windows-local integration that lets DeepSeek Harness users type `@`, choose a file already open in VS Code or Visual Studio, and send that file path to the model as a structured reference.
## Repository layout
-`protocol/`: versioned JSON snapshot contract shared by all components.
-`dsh-plugin/`: dual-face Cordis package. The Host reads snapshots; the Client registers the `@` source.
-`vscode-extension/`: VS Code companion using `window.tabGroups.all`.
The companions publish paths and dirty flags only. They never copy source text. DSH and the model continue to use the normal filesystem tools, so an unsaved IDE buffer is explicitly marked but is not silently substituted for the disk file.
The packaged DeepSeek Harness desktop app uses an isolated `DSH_HOME` below its Electron user-data directory. Set that path for the install command so the desktop sidecar, rather than only the default CLI profile, receives the bundle:
The package's `cordis.patch.yml` inserts its own shared Host/Client row. Fully quit and restart the matching DSH process after the first install. During development, run the DSH package watcher and the Harness `pnpm run dev:web` watcher when Client HMR is required.
Install the generated VS Code `.vsix` and Visual Studio `.vsix` from their component output directories. Once either IDE companion is active, type `@` in the DSH composer and select from the `IDE open files` group.
## Data and security boundary
Snapshots are stored under `%LOCALAPPDATA%\Prophet\dsh-plugin-coop-with-vs\v1\instances`. Writers update atomically and heartbeat every 15 seconds; the Host ignores snapshots older than 60 seconds. The DSH endpoint accepts loopback GET requests only, validates all snapshot fields, limits results, and never reads file contents while producing candidates.