DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

Logbook — DeepSeek Harness 插件(DSH Plugin)
← Plugins

dsh-logbook

Logbook

DeepSeek Harness 插件:提供 /logs 命令和 stderr 日志导出器,使 ctx.logger 输出实际可见

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

npx -y @deepseek-ai/dsh plugin --profile web add dsh-logbook@0.1.0
README兼容性版本

兼容性与来源证明

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

DSH 兼容范围
*
运行环境
any
发布来源
npm
Registry 更新时间
2026/9/20

版本

0.1.0stable
2026/8/31

相关插件

正在加载相关插件…

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

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

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

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

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

相关插件

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

DSCODE@toddzheng024/dscode-bundle完整的 DeepSeek 编码代理,支持持久化 shell、Ultra 协作和自动权限审查。Plugindsh-pluginDeepSeek Harness 社区插件市场,遵循官方插件规范——无需离开应用即可浏览、搜索并安装 9000+ 个由人工精选的社区插件。· DeepSeek Harness 社区插件市场(遵循官方开发规范):9000+ 人工精选社区插件,每日更新。Web App@deepseek-ai/dsh-web-appdsh 浏览器界面捆绑包:位于 dsh-base 之上的 Web 补丁层,加上运行时粘合插件(提供前端 dist、Web 界面提示符、bash 运行时变量和 URL 行)Sdk Minimal@deepseek-ai/dsh-sdk-minimal独立的最小 SDK 配置包:JSON-RPC、一个 DeepSeek 适配器、持久化 Shell 和 JSONL 会话

README

dsh-logbook

A DeepSeek Harness plugin that makes ctx.logger output visible: a /logs command in the chat, and a stderr exporter that is on by default for warnings and errors.

The problem it fixes

Every dsh plugin logs through ctx.logger, but no shipped profile mounts a log sink. The only default destination is a 1000-record in-memory buffer, and that buffer has a surprise: it silently drops warn and debug records. Cordis orders its levels error=0, info=1, warn=2, debug=3, and the buffer exporter falls back to each logger's default level of 1, so warnings never make it in. A plugin can warn about a real problem and there is no way to see it, live or after the fact (discussions #2905, #1241, #4994).

dsh-logbook registers one full-capture exporter (it asks cordis for everything, then filters itself) and gives you two views:

  1. stderr, live. By default only warnings and errors, so a healthy session stays silent. Open it up per plugin with a config map. Never writes to stdout, which stays free for SDK and ACP protocol traffic.
  2. /logs in the chat. The recent history (default ring of 2000 records, all levels), with filters:
/logs
/logs --level warn
/logs --name llm-gate --grep queue
/logs --since 10m --limit 100
logs: 3 of 41 records shown (ring 2000, buffer seeded 12)
14:01:59 llm-gate info llm-gate: llamacpp session=059a680f queued (depth 1)
14:02:03 llm-gate info llm-gate: llamacpp session=059a680f dispatched after 4012ms
14:02:11 llm-gate warn llm-gate: llamacpp session=059a680f queue full, rejecting

Install

dsh plugin --profile web add dsh-logbook

That is enough. To tune it, add to your profile's cordis.patch.yml:

- id: logs
  config:
    ring: 2000            # records kept for /logs
    stderr:
      enabled: true
      types:
        default: warn     # error | warn | info | debug | off
        llm-gate: debug   # everything from one plugin
        hmr: off          # silence one logger entirely

A value means "this type and anything more severe", in the order error, warn, info, debug. This deliberately differs from cordis's numeric levels, where info sits below warn and "warnings and errors only" cannot be expressed.

What you should know

  • The ring captures every level from the moment the plugin mounts, and seeds itself from the built-in buffer for anything earlier. Records from before the mount can only be error and info, because of the buffer behaviour described above.
  • The stderr writer attaches an error listener so a closed pipe (for example a dying tee) cannot crash dsh, and it never throws into the logging path.
  • Upstream note: cordis's ctx.logger.exporter() disposer currently removes the most recently registered exporter rather than its own, so any plugin reload can detach some other plugin's log sink. dsh-logbook keeps an internal flag so a stale copy of its exporter goes inert instead of double-reporting.
  • Related work: dsh-logger-panel is a web Settings page with rotating JSONL files; dsh-boot-doctor mounts a minimal console sink aimed at boot problems; dsh-o11y-plugin exports to OpenTelemetry. dsh-logbook is the terminal-and-chat option: filters, stderr, no web dependency, works headless.

License

MIT