DSH for VSCode

语言 / Language：中文 · English

中文

把 DeepSeek Harness（DSH） 完整搬进 VSCode：整个 Web GUI——聊天、会话、设置、以及全部 DSH 插件——以 iframe 嵌入编辑区面板，文件编辑与 VSCode 原生编辑器双向联动，并与浏览器 WebUI 共享同一个运行中的实例。

⚠️本项目由 Deepseek-V4-Flash 和 Deepseek-V4-Pro 生成，发布者仅测试其功能正常，不保证项目安全性⚠️

特性

• 完整 Web GUI，全部插件兼容——运行的是真实 dsh web 前端，由 iframe 嵌入到编辑区：聊天、会话、设置、模型与 agent preset，以及任何插件原样可用。
• 文件互通：
  • agent 创建/修改文件时，按策略在vscode编辑区打开对应文件；
  • 已打开且有未保存修改的文档不会自动覆盖；
  • 在编辑区保存后 agent 读到的就是最新磁盘内容；
  • 点击dsh中的交付文件 chips / 路径文本时，在vscode编辑区打开；
  • agent 删除文件时自动关闭对应文件标签页（dirty 则保留）；
  • 在 agent 中切换工作区时会将标签页切换到新工作区已打开的文件。
• 不改变profile——插件本身只是将web ui嵌入到vscode，不修改你 profile 的 package.json / cordis.patch.yml；卸载即无痕。

环境要求

• 桌面版 VS Code >= 1.90（Windows / macOS / Linux）。请注意，由于访问的是回环地址，Remote、容器与 vscode.dev 不受支持。
• PATH 上有 Node.js >= 20。
• 可用的 DSH 安装与已配置的 profile——npm i -g @deepseek-ai/dsh（或 npx 安装），且 ~/.dsh 已配置（settings / API key，dsh web 能正常启动）。扩展复用你现有的 ~/.dsh。

安装

从 VSIX 安装

npm install
npm run package        # 生成 dsh-for-vscode-<version>.vsix

然后在 VSCode 中：扩展视图 → ... → 从 VSIX 安装… → 重载。

快速开始

1. 命令面板运行 DSH: 打开 DSH 面板——面板在编辑器旁打开，DSH GUI（含你的全部插件）在其中启动。
2. 正常聊天。agent 写文件时自动在 VSCode 打开；点击聊天里的交付文件 chip 即在 VSCode 编辑器中打开。
3. 状态栏显示当前实例（DSH :端口），点击可随时重开面板。

实例共享

实例 即一个 DSH host 进程 。实例共享指的是VSCode与浏览器指向同一个DSH host 进程，从而获得相同的界面。该行为由设置项hostMode管理。

命令

设置（dshVscode.*）

项目结构

├─ src/                      # 扩展宿主源码（TypeScript → dist/）
│  ├─ extension.ts           # 激活、命令、组装
│  ├─ messages.ts            # 消息协议类型与守卫
│  ├─ host/
│  │  ├─ hostManager.ts      # spawn/connect/reattach/清理 + 叠加层生成
│  │  ├─ hostUtils.ts        # dsh 查找、端口、严格就绪探测
│  │  └─ dshApi.ts           # /api RPC 客户端（session.list → cwd）
│  ├─ webview/
│  │  ├─ panel.ts            # webview 面板、CSP、序列化恢复
│  │  └─ relay.ts            # 自包含的 iframe⇄宿主消息中继
│  └─ linkage/
│     ├─ nodeWatcher.ts      # fs.watch 递归目录监听（跨工作区）
│     ├─ watcher.ts          # 防抖、dirty 安全策略、tab 关闭
│     ├─ policy.ts           # 纯决策逻辑（glob→正则、打开决策）
│     ├─ pathSafety.ts       # 防目录穿越/符号链接的路径解析
│     └─ opener.ts           # 带行列的 showTextDocument
├─ bridge/                   # DSH 侧桥接插件（纯 ESM JS，无构建步骤）
│  └─ lib/
│     ├─ index.js            # cordis host 插件：/dsh-vscode 路由 + tapIndex + systemPrompt 公告
│     └─ bridge.js           # 页面内脚本：点击捕获、会话跟踪（dshEmbed 门控）
├─ tests/                    # node:test + jsdom 套件（74 个测试，零原生依赖）
├─ tools/
│  └─ session-log-check.mjs  # 会话日志检查/修复工具（corrupt session log: seq gap 恢复）
├─ .github/workflows/ci.yml  # CI：push/PR 时构建 + 测试
├─ package.json              # 扩展清单与脚本
└─ tsconfig*.json            # host（CJS）与 webview（普通脚本）配置

产物（dist/、node_modules/、*.vsix、.npm-cache/）已被 .gitignore 排除——其余全部提交。

已知限制

• 仅桌面版 VSCode；不支持 Remote / 容器 / vscode.dev。
• webview 内的下载（会话 ZIP）与剪贴板可能受 Electron 环境限制。
• 两个 VSCode 窗口共享工作区时，第二个窗口 reattach 到既有实例（不重复 spawn）。两个窗口同一时刻首次打开可能各起一个实例——先开一个面板即可避免。
• 桥接的点击捕获针对交付文件行（[data-produced-files-row]）与路径形 title——DSH 未来改版可能需要小幅更新（路径形过滤保证失效时安全放行）。

[!WARNING] 两个不同的实例上同时运行同一段对话可能会导致会话日志损坏

贡献

本项目由Deepseek Harness搭配Deepseek-V4-Flash和Deepseek-V4-Pro生成，发布者全程Vibe Coding，用于感受新模型搭配Harness的Vibe Coding体验。

许可证

MIT

English

Bring DeepSeek Harness (DSH) fully into VSCode: the entire Web GUI — chat, sessions, settings, and all DSH plugins — embedded in the editor area via an iframe, with two-way file sync to the native VSCode editor, and sharing the same running instance as the browser WebUI.

⚠️**This project was generated by Deepseek-V4-Flash and Deepseek-V4-Pro. The publisher has only verified that it functions and does not guarantee its security.**⚠️

Features

• Complete Web GUI, all plugins compatible — runs the real dsh web frontend, embedded in the editor area via an iframe: chat, sessions, settings, models & agent presets, and any plugin work exactly as-is.
• File interop:
  • when the agent creates/modifies files, the corresponding files open in the VSCode editor area per the policy;
  • documents that are open with unsaved changes are never overwritten automatically;
  • after you save in the editor, the agent reads the latest on-disk content;
  • clicking delivered-file chips / path text in DSH opens them in the VSCode editor area;
  • when the agent deletes a file, its editor tab closes automatically (dirty tabs are kept);
  • when the agent switches workspaces, tabs switch to files already open in the new workspace.
• No profile mutation — the plugin only embeds the web UI into VSCode; it does not modify your profile's package.json / cordis.patch.yml; uninstalling leaves no trace.

Requirements

• Desktop VS Code >= 1.90 (Windows / macOS / Linux). Note: because it accesses loopback addresses, Remote, containers, and vscode.dev are not supported.
• Node.js >= 20 on PATH.
• A working DSH install with a configured profile — npm i -g @deepseek-ai/dsh (or install via npx), with ~/.dsh configured (settings / API key, so dsh web starts properly). The extension reuses your existing ~/.dsh.

Installation

Install from VSIX

npm install
npm run package        # generates dsh-for-vscode-<version>.vsix

Then in VSCode: Extensions view → ... → Install from VSIX… → Reload.

Quick Start

1. Run DSH: Open DSH Panel from the command palette — the panel opens beside the editor and the DSH GUI (including all your plugins) starts inside it.
2. Chat normally. When the agent writes files they auto-open in VSCode; clicking a delivered-file chip in the chat opens it in the VSCode editor.
3. The status bar shows the current instance (DSH :port); click it to reopen the panel anytime.

Instance Sharing

An instance is a DSH host process. Instance sharing means VSCode and the browser point at the same DSH host process, getting the same UI. This behavior is governed by the hostMode setting.

Commands

Settings (dshVscode.*)

Project Structure

├─ src/                      # extension host source (TypeScript → dist/)
│  ├─ extension.ts           # activation, commands, wiring
│  ├─ messages.ts            # message protocol types & guards
│  ├─ host/
│  │  ├─ hostManager.ts      # spawn/connect/reattach/cleanup + overlay generation
│  │  ├─ hostUtils.ts        # dsh lookup, ports, strict readiness probing
│  │  └─ dshApi.ts           # /api RPC client (session.list → cwd)
│  ├─ webview/
│  │  ├─ panel.ts            # webview panel, CSP, serializer restore
│  │  └─ relay.ts            # self-contained iframe⇄host message relay
│  └─ linkage/
│     ├─ nodeWatcher.ts      # recursive fs.watch directory watching (cross-workspace)
│     ├─ watcher.ts          # debounce, dirty-safe policy, tab closing
│     ├─ policy.ts           # pure decision logic (glob→regex, open decision)
│     ├─ pathSafety.ts       # path resolution against traversal/symlink escapes
│     └─ opener.ts           # showTextDocument with line/column
├─ bridge/                   # DSH-side bridge plugin (plain ESM JS, no build step)
│  └─ lib/
│     ├─ index.js            # cordis host plugin: /dsh-vscode routes + tapIndex + systemPrompt notice
│     └─ bridge.js           # in-page script: click capture, session tracking (dshEmbed-gated)
├─ tests/                    # node:test + jsdom suite (74 tests, zero native deps)
├─ tools/
│  └─ session-log-check.mjs  # session-log check/repair tool (corrupt session log: seq gap recovery)
├─ .github/workflows/ci.yml  # CI: build + test on push/PR
├─ package.json              # extension manifest & scripts
└─ tsconfig*.json            # host (CJS) and webview (plain script) configs

Generated artifacts (dist/, node_modules/, *.vsix, .npm-cache/) are gitignored — commit the rest.

Known Limitations

• Desktop VSCode only; Remote / containers / vscode.dev are not supported.
• Downloads (session ZIP) and clipboard inside the webview may be restricted by the Electron environment.
• When two VSCode windows share a workspace, the second reattaches to the existing instance (no duplicate spawn). If both windows open a panel for the first time at the exact same moment, each may start its own instance — open one panel first to avoid it.
• The bridge's click capture targets the delivered-files row ([data-produced-files-row]) and path-shaped titles — future DSH UI redesigns may need a small update here (the path-shaped filter keeps it fail-safe).

[!WARNING] Running the same conversation on two different instances at the same time may corrupt the session log.

Contributing

This project was generated by the Deepseek Harness with Deepseek-V4-Flash and Deepseek-V4-Pro. The publisher vibe-coded all the way through, to experience the vibe-coding experience of the new models paired with the Harness.

License

MIT