DSH Plugin HubDSH 插件市场
Chinesezjc/dsh-tool-owned-render 预览 preview

Chinesezjc/dsh-tool-owned-render

Plugin插件 Native原生 ⭐ 2 MIT UI & Themes界面与主题

A design note and interactive prototype for making tool result rendering in an agent chat UI tool-owned: each tool self-registers its own React component on a keyed render slot and composes shared layout primitives, instead of a central skeleton owning a render-kind union.

catalog descriptioncatalog 简介 / catalog description：Design note and interactive prototype for tool-owned render: each tool owns its own result presentation, composing shared layout primitives instead of a central render-kind union.

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

The dsh-tool-owned-render plugin shifts tool result rendering to the tools themselves: each tool self-registers a React component on the keyed tool.call.toolview slot, composing the shared ToolCard, Segment, and Group primitives instead of relying on a central skeleton with a render-kind union. Use it when tool authors need to change or restructure their own presentation in isolation. A status lamp is offered as a helper derived from observation, not imposed. Two authoring paths are available: custom React, or a zero-code generic fallback.

DSH 插件 tool-owned-render 将工具结果渲染交由工具自身管理：每个工具在键控槽位 tool.call.toolview 中自行注册 React 组件，并复用 ToolCard、Segment、Group 三个布局原语，不再由中央骨架按 render-kind 分发。适用于希望工具作者可独立调整或重构各自呈现的场景。状态指示灯由观察式推导得出，作为辅助而非强制。可使用自带 React 或零代码通用回退两种方式实现。

View on GitHub在 GitHub 查看

Recommended强烈推荐 Send to your DSH发给你的 DSH 安装 
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-tool-owned-render（Chinesezjc/dsh-tool-owned-render）
仓库：https://github.com/Chinesezjc/dsh-tool-owned-render
本站详情页：https://www.yhbd.top/plugins/chinesezjc-dsh-tool-owned-render/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 2 · 最近提交 2026-08-20 · 主语言 TypeScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 warning1 项注意
  • Only 2 stars - very few users, little community feedback星标只有 2，几乎没人在用，遇到问题缺少社区反馈
DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

  • DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
  • External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
  • Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

  • Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
  • Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
  • curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
  • Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
  • Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
  • Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装 

dsh plugin --profile web add github:Chinesezjc/dsh-tool-owned-render

把 Chinesezjc/dsh-tool-owned-render 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

3.7 KB · 缓存于 2026-08-29 05:30:42 · 3.7 KB

tool-owned-render

A design note and interactive prototype for making tool result rendering in an agent chat UI tool-owned: each tool self-registers its own React component on a keyed render slot and composes shared layout primitives, instead of a central skeleton owning a render-kind union.

The design

Two principles decide the model:

  • A tool's presentation must be changeable in isolation.
  • A tool author keeps the right to restructure their own presentation.

A central skeleton with a shared render-kind switch fails both. So there is no central render dispatch and no render-kind union. Instead there are three layout primitives:

  • ToolCard — the card frame.
  • Segment — the core IN/OUT unit.
  • Group — optional; bundles Segments under one status lamp, for multi-execution tools.

Plus one observational status derivation offered as a helper (rather than imposed), and two paths for a tool author: write your own React, or get a generic zero-code fallback.

Read the note

The note covers the primitives, the lamp derivation, the two paths, the text-reconstructable data boundary, deferred extension points, alternatives considered, and a staged migration plan.

Prototype

prototype/unified-list-of-blocks-mock.html is a standalone interactive prototype — open it directly in a browser, no build step. It covers all tool shapes, Group cases, stress cases, and both authoring paths.

Tool-owned render, dark and light:

tool-owned render, dark

tool-owned render, light

The two paths — a tool composing its own React, versus the generic zero-code fallback:

two paths

The implementation

src/ is a working DSH client plugin built on this design: primitives (ToolCard/Segment/Group), the observation-derived lamp, and registrants that take over the keyed tool.call.toolview slot for read, bash, write/edit, grep/glob and web_search/web_fetch.

PLUGIN.md documents it: what each registrant renders, install and layering, takeover semantics, and the four things that need host changes and cannot be done from a plugin.

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 Chinesezjc/dsh-tool-owned-render 的 README.md。 在 GitHub 查看原文 →

Related相关推荐

← 上一个 Prev obsidian-workbench 下一个 Next BigFocus →