DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
B

@jasonqq/dsh-btw-plugin

Btw Plugin

用于 DeepSeek Harness 的 Codex 风格 /btw:向一个以对话为种子创建的子代理提问旁支问题,并将答案排除在主上下文之外

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

npx -y @deepseek-ai/dsh plugin --profile web add github:JasonQQ/dsh-btw-plugin#ee0d6fc213d06d92d152d0eea19fae6aaeb826fc
README兼容性版本

兼容性与来源证明

Btw Plugin 以 @jasonqq/dsh-btw-plugin 发布,当前版本为 0.1.2。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
github
Registry 更新时间
2026/10/1

版本

0.1.2stable
2026/10/1
0.1.1stable
2026/9/28
0.1.0stable
2026/8/25

相关插件

正在加载相关插件…

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

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

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

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

认领这个 Plugin →
报告问题

相关插件

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

MarketdshmarketDeepSeek Harness 内的可视化插件市场——浏览、搜索并一键安装社区插件。· DSH 可视化插件市场:浏览、搜索并一键安装社区插件。Better Sidebardsh-better-sidebarBetter Sidebar for DSH — 在一列中提供文件树、编辑器、变更、任务和侧边聊天,并为每个对话单独显示。同时提供服务,供其他插件注册侧边栏标签页和文件查看器。Client Ui Git Graph@linxin666/dsh-client-ui-git-graph外部 dsh Web GUI 插件:空会话 Git 分支选择器和 Git 图,包含实际的主机端 Git 操作与防护,作为 dsh 配置文件包Ssh@linxin666/dsh-sshdsh Web GUI 的远程 SSH 操作:主机配置存储(~/.dsh/dsh-ssh.json,可从 ~/.ssh/config 导入)、支持跳板主机的持久化 ssh2 连接池、exec / PTY Web 终端 / SFTP 传输 / 本地端口转发隧道 / 集群执行

README

@jasonqq/dsh-btw-plugin

A Codex-style /btw command for DeepSeek Harness.

/btw <question> answers a side question in a sub-context seeded with the main conversation, and shows the answer in the chat without ever adding it to the main conversation's model history. Ask "by the way…" questions freely — the main context stays clean.

How it works

  • The command is registered through @deepseek-ai/dsh-commands (the same registry that powers /compact, /goal, /plan).
  • The question is delegated through ctx.subagents.start("fork", …). The fork provider spawns a child agent seeded with the parent's completed turns, so the side question is answered with full knowledge of the main conversation.
  • The child's answer is returned as a plain command result. Command results are rendered by the UI adapter and never enter the model history — that is the "no pollution" guarantee.

Usage

In any session composer:

/btw <question>

The answer appears as a command result card. It does not become a message the main model sees, so you can reference it yourself without bloating the context.

Install

The plugin ships as a Cordis plugin and plugs into any profile that mounts @deepseek-ai/dsh-commands and @deepseek-ai/dsh-subagent (both are part of the shipped @deepseek-ai/dsh-base composition).

  1. Make the package resolvable from the profile, e.g. link it into the shared profile store:

    mkdir -p ~/.dsh/profiles/node_modules/@jasonqq
    ln -s "$PWD" ~/.dsh/profiles/node_modules/@jasonqq/dsh-btw-plugin
    
  2. Add it to the profile patch layer (~/.dsh/profiles/<profile>/cordis.patch.yml):

    - insert:
        - id: btw
          name: @jasonqq/dsh-btw-plugin
          config:
            provider: fork
    

    The profile patch is read at boot. In the desktop app, restart the app after editing it (the CLI dsh web runner hot-reloads its patches).

Compatibility

Harness (@deepseek-ai/dsh-*)cordisschemasteryStatus
0.2.0-rc.24.0.43.18.4✅ Verified — DSH Desktop 2.0.17, end-to-end /btw run (2026-10-01)
0.1.5-rc.24.0.23.18.2✅ Verified — DSH Desktop 2.0.13, end-to-end /btw run (2026-09-23)
0.1.1-rc.24.0.13.18.1✅ Verified — DSH Desktop 2.0.3

The command surface this plugin depends on — commands.register(), CommandInvocation, CommandResult, subagents.getProvider() / start(), SubagentRun.result / dispose(), SubagentResult.output / stopReason and the five stop reasons — is unchanged across those lines. The one difference in 0.2.0 is a tightening: SubagentResult.output is now readonly ContentBlock[], which this plugin's filter/map usage already satisfies.

Configuration

KeyDefaultMeaning
provider"fork"Subagent provider. fork seeds the child with the parent's completed turns (sees the main context); spawn starts a fully standalone child.
maxDepth(unset)Optional recursion-depth cap for the child; defaults to the harness default when omitted.

Development

npm test

The tests exercise the handler with a stubbed ctx.subagents seam — no live model or host is needed.

License

MIT