DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

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

dsh-langfuse

Langfuse

dsh-langfuse:DeepSeek Harness 的 Langfuse LLM 可观测性——每个代理会话对应一棵 OpenTelemetry 追踪树,并包含反馈评分和子代理谱系。

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

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

兼容性与来源证明

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

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

版本

0.1.1stable
2026/8/14
0.1.0stable
2026/8/14

相关插件

正在加载相关插件…

最新版
0.1.1
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
122 kB
文件数
8
Surface
any
许可证
MIT
发布源
npm
GitHub
★ 2
周下载
94
最近提交
2026/8/15
查看源码 ↗项目主页 ↗
README Badge

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

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

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

认领这个 Plugin →
报告问题

相关插件

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

Usage@linxin666/dsh-usagedsh Web GUI 的使用统计插件:检测各提供商余额和编码计划配额,并提供实时令牌使用记录,以及当前提供商的专属宠物气泡Whale Widgetdsh-whale-widgetDSH Web 界面右下角的 DeepSeek 余额小鲸鱼挂件:余额/今日已用/峰谷定价、自定义泡泡点击序列(文本/余额/今日/峰谷/图片/随机语句与并列加权选择)、逐行样式与字体、悬浮快捷编辑、音效与每轮消耗、自定义角色/动图/音效、吸附与翻转自定义Usage Stats@ychris12138/dsh-usage-statsdsh Web GUI 的令牌使用热力图、提供商余额和订阅配额Codex Connectdsh-codex-connect用于 DeepSeek Harness 的 ChatGPT OAuth 和 Codex 模型。

README

dsh-langfuse

Langfuse LLM observability for DeepSeek Harness — one OpenTelemetry trace tree per agent session, with feedback scores and subagent lineage.

Send every agent session to Langfuse as an OpenTelemetry trace tree — turn → trace, model step → generation, tool call → tool span — with GenAI semantic-convention attributes, token usage, time-to-first-token, and error statuses.

✨ Features

  • 🧵 Full session tracing — every turn, generation, and tool call lands in Langfuse with model, provider, usage (incl. cache-read & reasoning tokens), and TTFT.
  • 🚚 Content-Length transport — spans are delivered as a single write with an explicit Content-Length header, never chunked. Some Langfuse deployments sit behind gateways that mangle chunked POST bodies (400 Failed to parse OTel JSON Trace); this transport sidesteps that class of bugs entirely.
  • 👍 Feedback scores — /feedback records become TEXT scores on the session's latest turn trace.
  • 🔗 Subagent lineage — child-session turn traces link to the parent session's trace (same-process).
  • 🎚️ Three sharing modes — FULL (live), FEEDBACK_ONLY (export only when the user records feedback), DISABLED (default; nothing leaves the process).
  • 🔒 Opt-in inputs — generation input (system prompt / tools / prompt) is exported only when includeGenerationInput is on.
  • 🛡️ Fail-loud config — bad URLs, missing keys, and invalid bounds throw at plugin load, before any transport exists.

🚀 Quick Start

dsh plugin --profile web add dsh-langfuse

export LANGFUSE_PUBLIC_KEY=pk-lf-...
export LANGFUSE_SECRET_KEY=sk-lf-...
# optional: self-hosted or non-EU region
export LANGFUSE_HOST=https://langfuse.example.com

dsh web   # restart the running instance, then take a turn

With a key present the backend runs in FULL mode; without one it is DISABLED. LANGFUSE_TELEMETRY_MODE=FEEDBACK_ONLY narrows sharing to feedback-gated release, and LANGFUSE_INCLUDE_GENERATION_INPUT=1 exports generation inputs.

The bundled patch disables the base profile's session-telemetry-otel row (the telemetry seam accepts exactly one backend per context) and mounts this one. dsh --profile web --dump-config shows the composed result without booting.

As an explicit cordis.yml row

- id: session-telemetry-langfuse
  name: dsh-langfuse
  config:
    mode: FULL                 # FULL | FEEDBACK_ONLY | DISABLED (default)
    exporter:
      url: https://cloud.langfuse.com/api/public/otel/v1/traces
    auth:
      publicKey: !!js process.env.LANGFUSE_PUBLIC_KEY
      secretKey: !!js process.env.LANGFUSE_SECRET_KEY
    processor: {}              # optional; passed verbatim to BatchSpanProcessor
    includeGenerationInput: false

⚙️ Configuration

FieldDefaultMeaning
modeDISABLEDFULL exports every session live; FEEDBACK_ONLY exports the canonical session log only when feedback is recorded; DISABLED constructs nothing.
exporter.url—Full OTLP traces endpoint (…/api/public/otel/v1/traces). Required unless DISABLED.
exporter.timeoutMillis10000Per-request timeout.
auth.publicKey / auth.secretKey—Langfuse project key pair (Basic auth). Required unless DISABLED.
processor{}Passed verbatim to BatchSpanProcessor (scheduledDelayMillis, maxQueueSize, …). Retries (bounded backoff, 6 attempts) live in the exporter.
includeGenerationInputfalseExport langfuse.observation.input (system prompt / tool schemas / model / user prompt).
maxAttributeChars16384Per-attribute payload ceiling; longer payloads are truncated with a …[truncated] marker (the canonical log keeps the full bytes).
shutdownTimeoutMillis3000Deadline on the SDK's shutdown drain.
feedbackScoreNameuser-feedbackLangfuse score name for /feedback pushes.

🧭 What appears in Langfuse

dsh session eventLangfuse concept
turn/start / turn/endtrace (turn N; error end reasons → ERROR status)
step/start + request/header + assistant/messagegeneration (step T.S) — model, provider, output, gen_ai.usage.* tokens
first assistant/chunk of a steplangfuse.observation.completion_start_time (TTFT)
tool/call + tool/resulttool span (arguments → input, result → output, isError → ERROR)
user/messagetrace input
feedback/recordTEXT score on the session's latest turn trace
subagent session turnstrace links to the parent session's trace
agent-error ops recordexception event + ERROR status
every other event type (todo, plan, compaction, …)span event on the open turn

Correlation attributes use this package's own vocabulary (dsh.turn_idx, dsh.step_idx, dsh.event_seq, …) so multiple telemetry backends can share one Langfuse project without attribute collisions.

🏗️ How it works

  • A telemetry-seam backend. The harness logs everything model-visible to the canonical session log; this plugin implements SessionTelemetryBackend (@deepseek-ai/dsh-session-telemetry), so it captures every event — including ones it has never heard of — with the seam's consent semantics and redaction waterfall for free.
  • OTel SDK + custom exporter. Spans are built with BasicTracerProvider + BatchSpanProcessor, serialized with @opentelemetry/otlp-transformer, and delivered by a custom SpanExporter with Content-Length and bounded retries.
  • A folding timeline. SessionTimeline replays the flat record stream into span trees keyed by (session.id, turn, step). Span boundaries always use the record's own timestamp — live capture and canonical-log replay produce identical trees.
  • At-most-once delivery (inherited from the seam): the loss window is the crash window; receivers correlate on langfuse.session.id + dsh.turn_idx + dsh.event_seq.

🧪 Development

npm run check   # biome + typecheck + vitest (unit & seam integration) + build

30 tests cover config validation, the folding timeline, the transport (Content-Length, no Transfer-Encoding, retry/backoff), score pushes, and a full seam integration that drives a real SessionTelemetryCoordinator and asserts the wire payload.

⚠️ Limitations

  • One backend per context (the seam throws on duplicates — the bundled patch disables the official OTLP-logs row).
  • Subagent lineage is same-process best-effort (a resumed parent's trace id is unknown across restarts).
  • No durable delivery (at-most-once).
  • Score pushes are fire-and-forget (failures only log).

📄 License

MIT