DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

Btw — DeepSeek Harness 插件(DSH Plugin)
← Plugins
B

btw

Btw

DeepSeek Harness (DSH) 插件,在右侧边栏中添加并行侧边聊天,并继承主会话的工作区、工具、权限和模型。

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

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

兼容性与来源证明

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

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

版本

0.1.0stable
2026/10/19

相关插件

正在加载相关插件…

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

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

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

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

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

相关插件

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

Contextdsh-context用于上下文洞察和管理的 DeepSeek Harness 插件,提供上下文仪表板和上下文命令,帮助了解上下文的构成及其演变过程。Reme Dsh Plugin@agentscope-ai/reme-dsh-plugin面向 DeepSeek Harness 的 ReMe 记忆与上下文集成Memsearch Dsh@zilliz/memsearch-dsh适用于 DeepSeek Harness 的 MemSearch 插件:在多个代理之间共享 Markdown 记忆,支持捕获、步骤前上下文注入、记忆召回技能和技能候选审核面板。Memory@furongjun1999/dsh-memory灵枢(Lingshu·líng shū)DeepSeek Harness 插件:完整大脑——长期记忆/知识飞轮/自我认知/递归反思接入 DSH,对话自动沉淀进 md_cg 认知图(md 文档)

README

btw

btw is an external plugin for DeepSeek Harness (DSH), the desktop coding-agent app. It adds parallel side chats to the right sidebar of any DSH conversation. A side chat runs beside the main thread, inherits its workspace, tools, permissions, model, and reasoning effort, and starts with a digest of the main conversation. The side-chat tab renders the shared conversation surface, so composing, queuing, attachments, tool cards, Markdown, and scrolling behave exactly like the main thread.

Requirements

  • DeepSeek Harness 0.2.1-rc.1 or newer (the engines.dsh floor in package.json).
  • A DSH profile to install into; the desktop profile is shown below.
  • btw is not a standalone app: the host half runs inside the DSH host, and the client half is a DSH Web client plugin. It plugs into DSH's resources, sessions, sidebarRightTabs, sidebarRight, slots, commandUi, shortcuts, and locale services, and renders DSH's shared conversation.content factory.

How it works

  • A side chat is an ordinary hidden Session: meta.parentSession records lineage, and the session is archived right after creation, so it stays out of the session lists.
  • The client does not paint a custom chat panel. Each side chat is a resource tab:
    • address: dsh-resource://btw/session/<child>?parent=<parent>
    • the resource provider calls /attach first (so the child Agent is live), refreshes the session catalog, then sessions.retain()
    • the tab body binds the child with SessionProvider and renders conversation.content with variant: 'embedded'
    • therefore the composer, image paste/attachments, queued messages, tool cards, thinking, Markdown, and scroll-follow all come from the main-thread components
  • Archive and sending: the shared Composer prompts the child session directly. A prepended agent/pre-step listener unarchives the child before the archived-session gate runs; agent/status re-archives it once the agent is idle.
  • Context is injected as system-prompt sections: at fork time the host reads the parent transcript, keeps roughly the last 10 messages / 6000 characters, and adds btw:context (interpolate: false) plus btw:role. Reattaching a chat re-reads the parent and refreshes the digest.
  • Inheritance: agentPresets.composeFrom(agentCtx, parent.ctx) copies tools and prompt sections; permissionPresets copies the access policy; the model route comes from the parent's request/header (falling back to agentDefaultModel). The child is accounted into the parent's Workspace and seeded with a model/selection event so the shared composer does not ask for a workspace and shows the same model/effort.
  • Many side chats per main conversation: one tab per chat; GET /state lists them all. A tab's × runs registerCloseHandler and closes the chat (dispose + tombstone), so it never comes back after a restart.
  • Restart recovery: /state re-registers every btw-* child of the parent from disk (skipping tombstones). The resource calls /state before /attach; attach resumes the agent with composeFrom and the context sections, so a resumed side chat keeps the same tool surface.
  • Tombstones live in ~/.dsh/btw/closed.json (honoring DSH_HOME).
  • Delivery between sessions uses agent tools, not HTTP:
    • send_to_main (side chat) sends [side chat <childId>] ... to the main conversation as a user message.
    • send_to_side (main thread) sends [main thread] ... to the most recent side chat, or to childId when given. Both call followup in-process; there is no loopback delivery route.
  • The client depends only on react; everything else comes from cordis services (resources, sessions, sidebarRightTabs, sidebarRight, slots, commandUi, shortcuts, locale).

Install

dsh plugin --profile desktop add /path/to/btw

After changing code, run pnpm build and restart the app. The host snapshots client bundles at boot, so reloading the page is not enough.

Usage

UI copy comes from the DSH locale service (zh/en) and follows the app language; it is not hardcoded in the component.

  • ⌘⌥S, /side, or /btw: open the most recent side chat; create one when none exists.
  • The + in the tab header starts another side chat.
  • Closing the tab's × closes and deletes that side chat.
  • The tab title follows the session title after the first message; before that it reads "Side chat".
  • The main thread can call send_to_side; a side chat can call send_to_main.

Limits

  • The context is a snapshot taken at attach time; later messages in the main conversation are not synchronized automatically.
  • DSH's session persistence layer has no delete API, so closing a side chat only disposes the agent and writes a tombstone; the btw-* log stays under ~/.dsh/sessions.
  • Host routes accept loopback requests only.

Development

pnpm install
pnpm typecheck
pnpm test
pnpm build