DeepSeek Harness 插件

nexusclaw-agent-governance

DeepSeek Harness (dsh) approval answerer backed by the agent-governance sidecar — every approval/request is decided by the deny-by-default gate, L0–L4 rules and the organizational audit chain.(英文原文)

跳到安装方式

来源信息

GitHub 仓库
NexusClawHQ/nexusclaw-agent-governance
最近更新
2026年8月18日
分类
自动化与任务
GitHub stars
1
载体类型
plugin
包路径
governance/adapters/dsh-plugin
目录证据
上游声明已找到 dsh.bundle
证据路径
governance/adapters/dsh-plugin/package.json#dsh.bundle
核对版本
0.1.0-rc.8
上游核对日期
2026-08-20

该证据由上游目录提供。本站没有安装、运行或安全审核这个插件。

安装

默认先复制一段 Prompt,让 Agent 读 GitHub 仓库和源码;需要自己装时再切到命令。

复制这段 Prompt,发给 DSH、Codex 或其他 Agent,让它先读 GitHub 仓库和源码。

请先不要安装或执行任何命令。阅读这个插件的 GitHub 仓库、README 和关键源码,然后用清楚、直接的方式回答以下问题,帮助我判断它是否适合我的需求:

1. 这个插件是什么,解决什么问题;
2. 适合哪些用户和典型使用场景;
3. 安装后如何使用,并给出一个最小使用示例;
4. 有哪些已知限制,以及隐私、安全、兼容性或维护风险;
5. 给出“推荐 / 有条件推荐 / 不推荐”的明确建议和理由。

请区分仓库明确说明、根据源码推断和未知信息。证据不足时请明确说明,不要猜测或照抄 README。

GitHub:https://github.com/NexusClawHQ/nexusclaw-agent-governance/tree/HEAD/governance/adapters/dsh-plugin
插件名:nexusclaw-agent-governance
作者:NexusClawHQ

检查来源文件

安装前先看这个插件目录里的 README 和其他文件。

文件资源管理器2 个文件
README.md来源说明 · 只读预览

dsh-plugin-governance-gate

A DeepSeek Harness (dsh) approval answerer backed by the agent-governance sidecar: every dsh approval/request is decided by the deny-by-default gate, L0–L4 risk rules and the organizational audit chain — with human approvals happening in the sidecar console instead of (or in addition to) dsh's own UI.

Spike conclusions (spec mcp-governance-gateway, Phase I1)

Verified against the dsh source and docs on 2026-08-18:

  • dsh's user-approval seam exposes a waterfall answerer event

'approval/request'(req, next) where a listener claims the request by

returning an ApprovalOutcome (`'allowed-once' | 'rejected' | 'cancelled' |

'unavailable') or delegates via next(); the chain is fail-closed (missing/throwing answerers resolve 'unavailable', callers deny). Source: packages/interaction/user-approval/src/index.ts` in the dsh repo.

  • Plugins ship as npm packages with a dsh.bundle manifest

(dsh: { bundle: { patch: "./cordis.patch.yml" } }), an ESM entry exporting name + apply(ctx), installed via dsh plugin add. Source: docs/user/develop/basic/publish.md.

  • Semantic alignment is exact: our gate's allow / blocked / paused maps

1:1 onto allowed-once / rejected / wait-for-human. No degradation to a docs-only recipe was needed.

Known v1 limitation (by dsh design): ApprovalRequest deliberately omits tool arguments (they are linked via callId), so input-matching risk rules see only the call reference, not the rendered arguments.

Install (into a dsh profile)

# 1. run the governance sidecar (one command, zero config):
npx @agent-governance/sidecar          # or the single-container Docker image
# 2. add the answerer to your dsh profile:
dsh plugin add dsh-plugin-governance-gate
# 3. point it at the sidecar (default http://127.0.0.1:7899):
export GOVERNANCE_SIDECAR_URL=http://127.0.0.1:7899

Grant the dsh tool names at the gate (deny by default), e.g.:

SIDECAR_GATE_ALLOWED_TOOLS="bash,read,write" npx @agent-governance/sidecar

Behavior

Gate verdictdsh outcome
allowallowed-once — dsh executes the tool locally
blockedrejected — the denial lands on the audit chain
paused (L2/L3)waits for the human in the sidecar console; approved → allowed-once, rejected → rejected
sidecar unreachable / wait timeoutnext() — dsh's own answerers stay in charge (still fail-closed); set GOVERNANCE_FAIL_CLOSED=1 to hard-reject instead

Env knobs: GOVERNANCE_SIDECAR_URL, GOVERNANCE_POLL_MS (default 1000), GOVERNANCE_TIMEOUT_MS (default 600000), GOVERNANCE_FAIL_CLOSED.

Apache-2.0. Parent project: agent-governance.