DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Bat2exe — DeepSeek Harness 插件(DSH Plugin)
← Plugins

dsh-bat2exe

Bat2exe

在 DeepSeek Harness 中将 Windows .bat/.cmd 启动器编译为真正的 .exe 外壳:渲染图标、生成 C# 包装器、使用 csc.exe(或 dotnet)编译,并安装开始菜单/桌面快捷方式。

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add dsh-bat2exe@0.1.1
README兼容性版本

兼容性与来源证明

Bat2exe 以 dsh-bat2exe 发布,当前版本为 0.1.1。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
npm
Registry 更新时间
2026/9/12

版本

0.1.1stable
2026/9/12

相关插件

正在加载相关插件…

最新版
0.1.1
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
33.2 kB
文件数
7
Surface
any
许可证
MIT
发布源
npm
GitHub
★ 0
周下载
0
最近提交
2026/9/12
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录

相关插件

继续浏览 developer-tools 分类下经过校验的插件。

DSCODE@toddzheng024/dscode-bundle完整的 DeepSeek 编码代理,支持持久化 shell、Ultra 协作和自动权限审查。Plugindsh-pluginDeepSeek Harness 社区插件市场,遵循官方插件规范——无需离开应用即可浏览、搜索并安装 9000+ 个由人工精选的社区插件。· DeepSeek Harness 社区插件市场(遵循官方开发规范):9000+ 人工精选社区插件,每日更新。Web App@deepseek-ai/dsh-web-appdsh 浏览器界面捆绑包:位于 dsh-base 之上的 Web 补丁层,加上运行时粘合插件(提供前端 dist、Web 界面提示符、bash 运行时变量和 URL 行)Sdk Minimal@deepseek-ai/dsh-sdk-minimal独立的最小 SDK 配置包:JSON-RPC、一个 DeepSeek 适配器、持久化 Shell 和 JSONL 会话

README

dsh-bat2exe

Turn a Windows .bat / .cmd launcher into a real .exe — from inside DeepSeek Harness.

The EXE is a thin shell: it locates the batch file next to itself and hands the whole job to cmd.exe. The launcher logic stays editable text, no tool path is baked into the binary, and upgrading whatever the batch file calls needs no recompilation.

Install

dsh plugin --profile web add dsh-bat2exe

Restart DSH, then ask the agent to build a launcher — or call the tool directly.

Tools

bat2exe_build

ParameterMeaning
batrequired — path to the .bat/.cmd file (absolute, or relative to the working directory)
nameoutput executable name; defaults to the batch name with .exe
iconTextup to four characters drawn on a generated icon
iconTextColouricon text colour as #rrggbb
iconuse an existing .ico instead of rendering one
startMenuShortcutalso write a Start Menu shortcut
desktopShortcutalso write a Desktop shortcut

The build runs four steps, all local and offline:

  1. Icon — renders a rounded-square plate with a diagonal gradient and the given text, using a built-in 5×7 bitmap font, then packs it as a 256×256 ICO. No image library, no external tool.
  2. C# shell — emits a wrapper whose only job is to run the batch file from its own directory, forwarding all arguments and preserving the exit code.
  3. Compile — csc.exe from the .NET Framework (falling back to dotnet build when only the .NET SDK is present), with the icon embedded as a resource.
  4. Shortcuts — optional .lnk files, written through WScript.Shell.

bat2exe_probe

Reports the local toolchain — C# compiler path, .NET SDK presence, PowerShell, and the resolved defaults — so a failure can be diagnosed before a build is attempted.

Settings

bat2exe registers a settings namespace, so defaults are editable in Settings → Plugins rather than by hand-editing a profile patch:

KeyDefaultMeaning
iconTextBATtext drawn on a generated icon
iconFrom / iconTo#12204a / #4a6cf7gradient start / end
workDir.bat2exewhere *.cs, *.ico and other by-products go
startMenuShortcutfalsedefault for the Start Menu shortcut
desktopShortcutfalsedefault for the Desktop shortcut

Per-call tool arguments always win over these defaults.

Requirements

  • Windows. The pipeline compiles a Windows PE and writes .lnk files.
  • A C# compiler: .NET Framework 4.x (csc.exe, present on stock Windows) or the .NET SDK.
  • PowerShell for shortcut creation only (pwsh preferred, Windows PowerShell accepted).

bat2exe_probe reports exactly which of these were found.

What gets written

Everything lives next to the batch file, so a launcher folder is self-contained:

DSH-Web.bat            <- your launcher (unchanged)
DSH-Web.exe            <- the compiled shell
.bat2exe/
  DSH-Web.ico          <- generated (or your supplied) icon
  DSH-Web.cs           <- the emitted C# source, kept for inspection

License

MIT