DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

Plugin Compact Button — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
P

dsh-plugin-compact-button

Plugin Compact Button

用于 DeepSeek Harness Web UI 的 Composer 压缩控制:模型选择器旁的按钮,用于运行部署自身的 /compact 命令。

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

npx -y @deepseek-ai/dsh plugin --profile web add github:liutian11451-png/dsh-plugin-compact-button#5df2213b5af6fb63a168e054a117d003aeb02657
README兼容性版本

兼容性与来源证明

Plugin Compact Button 以 dsh-plugin-compact-button 发布,当前版本为 1.0.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
web
发布来源
github
Registry 更新时间
2026/9/11

版本

1.0.0stable
2026/9/11

相关插件

正在加载相关插件…

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

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

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

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

认领这个 Plugin →
报告问题

相关插件

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

Web App@deepseek-ai/dsh-web-appdsh 浏览器界面捆绑包:位于 dsh-base 之上的 Web 补丁层,加上运行时粘合插件(提供前端 dist、Web 界面提示符、bash 运行时变量和 URL 行)Experimental Agent Team Web Profile@deepseek-ai/dsh-experimental-agent-team-web-profile用于 Agent Teams Remote 和 UI 插件的实验性 Web 配置层Remote Web Ui@linxin666/dsh-remote-web-ui通过扫码配对访问 dsh Web GUI,共享一个官方界面:设置按钮旁的二维码可将手机和 PC 配对到同一个 Web GUI(手机采用竖屏触控适配层,PC 使用完整桌面界面),通过一次性令牌和 rClient Ui Task Board@linxin666/dsh-client-ui-task-board面向 DSH Web GUI 的主机权威任务面板,支持实际会话执行、主机 cron 调度以及可选的跨平台空闲睡眠保护;以挂载方式提供,无需修改 DSH 源代码。

README

dsh-plugin-compact-button

English | 中文

A compact control for the DeepSeek Harness web composer: one button, seated directly left of the model selector, that runs the deployment's own /compact command.

What it does

Click it and the session compacts. The button submits the bare /compact line over the Session's command channel, which means the durable attempt record, the compaction lock, the summarization route, and the flow node the Chat view already renders all stay exactly the ones /compact owns. This plugin contributes the gesture and its localized refusals — never a second compaction path.

  • Blank session — renders nothing; there is no history to compact.
  • Agent running — greyed out and unclickable, keeping its ordinary label. Manual compaction needs an idle agent, but a turn this control did not submit must not claim to be compacting.
  • Compacting — reads Compacting… from the gesture until the compaction turn ends, then returns to its ordinary label. The window is a three-step latch: the gesture arms it, the observed run confirms it, the run ending releases it. Watching the run alone is not enough — a compaction admitted while the agent was already running never shows the control a run starting, which is the case that once left the label stuck after the compaction had finished.
  • Refused — one inline reason above the composer row. A transport failure shows the host's own message; a deployment with no /compact command is reported as the missing capability rather than appearing to succeed.

Install

dsh plugin --profile web add dsh-plugin-compact-button

Substitute your profile name for web if you run a different one. The package declares dsh.bundle, so dsh plugin registers its patch layer in the profile automatically. Restart dsh web and reload the page; the build payload is composed at boot, so a reload alone is not enough the first time.

From a GitHub checkout

dsh plugin --profile web add github:liutian11451-png/dsh-plugin-compact-button

A git install fetches sources, not built artifacts, so the package ships a prepare script that builds lib/ from src/ with plain tsdown — no sibling repository, no type checking. pnpm ≥10 refuses to run a git dependency's prepare until you allow it, so the first add fails with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED and prints the exact key to add. For a git install that key names the resolved tarball, not the bare package name:

allowBuilds:
  dsh-plugin-compact-button@https://codeload.github.com/liutian11451-png/dsh-plugin-compact-button/tar.gz/<commit-sha>: true

Copy the line pnpm prints verbatim — it carries the commit the install resolved to — then re-run the add. Treat that allowance as permission to execute this package's code on your machine at install time, and pin a commit (github:liutian11451-png/dsh-plugin-compact-button#<sha>) so a later push cannot silently change what runs.

One caveat when moving an existing install: if the plugin was previously installed from a local directory, remove that first. A leftover link in the profile's node_modules collides with the incoming git install and pnpm fails with an EPERM symlink error during import.

To avoid asking users for the allowance altogether, publish to npm or ship a tarball from pnpm pack — neither needs build permission.

Local directory

dsh plugin --profile web add /absolute/path/to/dsh-plugin-compact-button

Requirements

The deployment must mount the compaction capability — dsh-command-compact plus a compaction backend. Both are part of the standard preset. Without the command the button still renders and answers a click with an explicit unavailable-capability reason; the client cannot know the host's command catalog up front.

Layout

package.json                                # dsh.bundle + dsh.client manifests
cordis.patch.yml                            # inserts this package's loader row
src/index.ts                                # node half (inert)
src/client/index.ts                         # browser half: registers the seat
src/client/CompactButton.tsx                # the control
src/client/locales.ts                       # zh/en dictionaries
src/client/CompactButton.module.css         # chip chrome and the refusal strip
tsdown.config.ts                            # consumer-side build
smoke.mjs                                   # loader-contract smoke test

The node half is deliberately empty. The harness client module registry discovers dsh.client packages by walking the host Loader's rows, so the package needs one mounted row as its carrier; that is all the row is for.

Development

pnpm install
pnpm build       # emits lib/index.js and lib/client.js
pnpm typecheck
node smoke.mjs   # evaluates the built browser half against a stub shell

smoke.mjs checks the two contracts that are easy to break and invisible until boot: the artifact must take the window.__ModuleLoader__.load({ id, factory }) handoff and return module.exports, and apply() must register one conversation.input.right entry whose injected verb submits /compact and folds all three admissions into copy.

The two build contracts

The browser bundle is not an ordinary ESM build. The shell fetches lib/client.js and evaluates it, so the file must be a CommonJS closure factory — hence the banner, intro, and footer in tsdown.config.ts. An ESM or unbannered artifact throws at boot.

Specifiers the shell's module table answers (react, react/jsx-runtime, cordis, the shared UI primitives and store) stay require(...) calls; everything else is inlined. A require the table cannot answer is a guaranteed runtime throw, which is why the external list in the build config is explicit rather than derived from the package's dependencies.

Known limitations

  • The gesture is only as available as the command — a deployment without dsh-command-compact renders the button and answers a click with the unavailable-capability reason.
  • Admission is not completion — the command RPC resolves when the host admits the line, so the Compacting… label covers the window from the gesture to the end of the compaction turn. A compaction started by an automatic policy, or any other turn, leaves the label alone; the control is merely greyed out while that turn runs.
  • The busy label is bounded, not exact — an admitted attempt that never produces an observable run releases after an 8-second grace period, because the client is not shown a compaction lifecycle it could wait on. A compaction that starts later than that reads as this control going idle early.
  • No region selection — the control always submits the argument-free form, so it compacts the backend's own useful range and never a hand-picked span.
  • Idle agents only — disabled while the agent runs, matching compactNow's requirement; it is not a way to force compaction mid-turn.
  • Web profile only — declared platform: web; there is no terminal-surface equivalent.

License

MIT