This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.

Quick start

dsh-web-ui-all

— source: plugin_wiki.wiki_content

Install & verify

dsh plugin --profile web add @linxin666/dsh-web-ui-all

Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.

— source: plugins.install

Key points

• 可靠 Windows 启动：移除 PowerShell 5.1 -WindowStyle Hidden 与 Electron Node 模式的冲突，隐藏窗口仍由 spawn 的 windowsHide 处理；空旧补丁、状态订阅竞态和 IPC 错误不会再把启动页永久留在 8%。
• 验证过的 Runtime 组合：内置 @deepseek-ai/dsh 0.1.0-rc.7、dshmarket 1.15.0、Web UI 聚合 0.2.3、兼容 rc.7 的 Codex Connect 与 dsh-live-stats 0.1.20，Stable 继续精确锁定而非追随 latest。
• 托盘与后台自动化需显式选择：默认关闭仍会退出。选择“最小化到托盘并启用后台自动化”后，关闭主窗口才保留 Runtime 和到期任务；显式退出、更新、安全模式和崩溃路径一律完整停止。
• Host 持久任务调度：Task Board 保存时区、cron 槽位、租约、misfire/running 策略和确定性运行键；启用后台自动化时通过真实 DSH Session 执行并回写 Task Run，Host 不可用时仍回退浏览器调度。
• 可审计的扩展边界：扩展坞校验 dsh.compatibility 的版本、Desktop API、能力、Surface 与运行时证据，并在 profile 写入 desktop-plugins.lock.json。browser-safe SDK 不导入 Electron 或私有 DSH 模块；预览的外部打开仅传工作区根和相对路径，Host 验证后才交给系统。

— source: plugin_wiki.readme_en (fallback readme_raw)

FAQ

What else needs to be done after installation for the plugin to take effect?

Restart dsh web. If using source code development mode, besides dsh plugin add, you also need pnpm install && pnpm -r build && node scripts/link-profile.mjs, and restart dsh web after installation for it to take effect (README.md:24-30).

What if I only want to install one or two plugins, not the entire bundle?

You can directly install the corresponding standalone sub-package (e.g., dsh plugin add @linxin666/dsh-client-ui-task-board), instead of using this bundle; installing this package will activate all sub-plugins and you cannot select only some of them (README.md:34).

Will there be conflicts when installing with a standalone plugin package of the same name?

Yes, there will be conflicts. The aggregated package id is exactly the same as the standalone sub-package id (e.g., task-board, pet), so it cannot be installed together with the corresponding standalone package; before switching, first run dsh plugin remove on the old package (README.md:36).

How to troubleshoot when the new version doesn't take effect after upgrading?

After changing the version number in the profile's package.json and executing pnpm install, the top-level node_modules/@linxin666/* entries may still be linked to the old store directory. Need to confirm these links point to the new version (Windows: cmd /c rmdir then cmd /c mklink /J ), then restart dsh web (README.md:32-34).

What custom logic is actually installed in this package code?

The host side has no business logic (the apply function at src/index.ts:14 is an empty function); the browser side only has a compat shim (src/client/index.ts:1-98), which adds old-style data-pane/data-dsh-frame attributes to the dsh web shell's sidebar/middle/detail three-column containers, allowing sub-plugins mounted with old selectors to continue working.

Will this package still work after the official dsh web shell is upgraded?

Yes. The compat shim uses MutationObserver to listen for DOM changes and merges/reapplies attributes in the next frame (src/client/index.ts:64-71). After React re-renders and rebuilds the column containers, it will automatically restore the attributes, and the operation is idempotent so it won't trigger repeatedly.

— source: plugin_wiki.faq_json

Compatibility

• DSH: 未声明（package.json 无 dsh.engines；DSH 版本通过 @deepseek-ai/* SDK 依赖隐式锁定）
• Node: ^22.19 || >=24（据 packages/AGENTS.md:9，本包 package.json 未声明 engines）

— source: plugin_wiki.compatibility_json

Pitfalls

Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.

— source: general rule