harness-ops
DeepSeek Harness 的可审计运行证据和运维仪表板
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:AikingChoice/harness-ops#220399941dd6c3933ecc2501cc5dbacfd6550539Harness Ops 以 harness-ops 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →Auditable run evidence and a local operations dashboard for DeepSeek Harness.
DeepSeek Harness 的计划与结果记录插件：记录步骤、保存命令输出、汇总检查结果， 并通过本地网页查看。适用于不同语言的工程任务，目前为早期可用版本。
HarnessOps records an engineering agent's plan and reported command results, then computes a summary for human review. It does not replace the DeepSeek Harness agent loop, sandbox, command tools, sessions, or approval flow.
Agent demos often collapse plans, model claims, and observed command results into one transcript. HarnessOps keeps those layers separate:
Goal -> Recorded plan -> Host approval/execution -> Bounded evidence
-> Integrity verification -> Deterministic result -> Dashboard
The final status is computed from recorded evidence:
passed: every planned step has passing evidence.failed: at least one executed step failed or timed out.inconclusive: a step is missing or explicitly not run.Missing evidence cannot produce a passing result. However, evidence is currently
submitted by the caller (including the model), not captured from host execution
events. A caller can submit fabricated output. A passed result means that all
recorded outcomes passed, not that HarnessOps independently verified execution.
| Tool | Responsibility |
|---|---|
ops_run_start | Open one durable run for a goal and workspace. |
ops_plan_record | Store the exact plan before execution. |
ops_evidence_record | Store one bounded, redacted command result. |
ops_run_finalize | Verify evidence hashes and compute the terminal status. |
DeepSeek Harness remains responsible for asking approval and executing the planned command through its normal tools. HarnessOps only records the result.
Requirements:
pnpm install
pnpm check
pnpm demo
pnpm build
node dist/cli.js demo
node dist/cli.js serve
Open http://127.0.0.1:4177 to inspect recorded runs.
The demo command creates synthetic records without running checks. Their
limitations are visible in the dashboard. It is only a preview dataset.
Install the packed plugin into a Harness profile:
pnpm pack
dsh plugin --profile headless add ./harness-ops-0.1.0.tgz
Set HARNESS_OPS_DATA_DIR to move the local evidence directory. The default is
.harness-ops under the host working directory.
Inspired by AgentForge, HarnessOps keeps its useful ideas: structured plans, human-controlled execution, bounded evidence, auditability, and deterministic reporting. It removes the duplicate agent runtime, model transport, Windows-only launcher, machine-specific paths, and silent demo-data fallback.
pnpm test:coverage checks persistence races, result aggregation, credential
redaction, output bounds, HTTP reads, and plugin dispatch. The integration test
uses the real Cordis, SystemPrompt, and ToolRuntime services with synthetic
results; it does not call a paid model or prove host command execution.
GitHub Actions runs type checking, tests, build, and package creation on Node 22.19 and 24. There is no model-backed end-to-end test in this release.
MIT