vibeinging/deepseek-harness-desktop-app--packages-dsh-work-shell111

@deepseek-ai/dsh-work-shell

DeepSeek Harness Desktop App root Client Plugin for the current DSH Web Profile

AI 분석

核心用途是构建桌面端应用的主体框架。适合需要将官方 Web 运行时平滑过渡到桌面窗口布局、统一管理设置的桌面端用户。

패키지
@deepseek-ai/dsh-work-shell
버전
0.0.1
라이선스
MIT
최근 업데이트
2026. 8. 15.

설치

$npx -p @deepseek-ai/dsh dsh plugin --profile web add github:vibeinging/deepseek-harness-desktop-app#a7cfa02b2937730fd3e3d75b97524550afa957f7&path:packages/dsh-work-shell

@deepseek-ai/dsh-work-shell

This private Profile Bundle appends one dual-face row to the official DSH Web Profile. The official @deepseek-ai/dsh-web-app runtime and @deepseek-ai/dsh-web-frontend keep ownership of the page, server, transport, Client graph, and boot lifecycle. The Bundle disables the official ui-layout, ui-sidebar, ui-conversation, and duplicate ui-settings-general page shells, then the browser half owns the visible root, provides the layout service adapter, and declares the standard child Slots. Its General section entry owns settings.general.item; the existing product settings page renders that child through the authorized parent entry. The product Plugins route renders the Profile's existing Plugins section instead of redeclaring its settings.plugins.tab child.

The visible product currently renders settings.section, settings.general.item, Profile-owned settings.plugins.tab, shell.overlay, sidebar.footer.action, conversation.composer.dock, and the product-owned agent.workbench.tool. The sidebar adapter keeps DeepSeek Harness Desktop App's workspace and settings UI, while additive DSH footer actions appear beside the existing settings button. The conversation adapter keeps the existing product message and composer UI, selects the exact DSH Client Session bound to the product conversation, and exposes only the read-only additive composer dock with the official Session queue snapshot. Interactive input and message Slots remain unsupported until they can reuse the same Session command path without introducing a second input or queue owner. The product Models route renders the official DSH Models section when it is present. Theme and locale state come directly from the shared DSH Client services; App storage is only a standalone-development fallback. details is declared for dependency activation but is not rendered by the product shell. The package is App-managed and mounted only through the Profile bundle list. Its browser bundle must be fetched through DSH's /plugins//client.js route; it is not a standalone page.