DeepSeek Harness 插件

JARVIS-Mission-Control-DeepSeek

DeepSeek-Harness (dsh) plugin that streams sessions, turns, and tool activity to a JARVIS Mission Control board(英文原文)

跳到安装方式

来源信息

GitHub 仓库
Asif2BD/JARVIS-Mission-Control-DeepSeek
最近更新
2026年8月20日
分类
工具与能力
GitHub stars
1
载体类型
plugin
包路径
integrations/deepseek-harness/dsh-plugin-mission-control
目录证据
上游声明已找到 dsh.bundle
证据路径
integrations/deepseek-harness/dsh-plugin-mission-control/package.json#dsh.bundle
核对版本
0.1.0-rc.8
上游核对日期
2026-08-21

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

安装

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

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

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

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

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

GitHub:https://github.com/Asif2BD/JARVIS-Mission-Control-DeepSeek/tree/HEAD/integrations/deepseek-harness/dsh-plugin-mission-control
插件名:JARVIS-Mission-Control-DeepSeek
作者:Asif2BD

检查来源文件

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

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

dsh-plugin-mission-control

Mirror DeepSeek-Harness (dsh) agent activity onto a live JARVIS Mission Control board: every dsh session becomes a task, messages and tool calls stream into the activity log, and finished turns land in REVIEW for a human to approve.

Validated against @deepseek-ai/dsh@0.1.0-rc.7 — both the shipped type definitions and a live headless run. dsh is a developer preview; event names are config-overridable so upstream renames are a config fix.

Install

# Into a dsh profile — the plugin self-activates via its dsh.bundle declaration.
# Pin the currently validated dsh preview, or use `dsh plugin ...` if already installed.
npx @deepseek-ai/dsh@0.1.0-rc.7 plugin --profile web add dsh-plugin-mission-control

# Point it at your board (defaults shown)
export MISSION_CONTROL_URL=http://localhost:3000
export MC_AGENT_ID=agent-dsh
export MC_AGENT_TOKEN=...   # only if your board enforces auth

npx @deepseek-ai/dsh web

Need a board? git clone https://github.com/Asif2BD/JARVIS-Mission-Control-DeepSeek && cd JARVIS-Mission-Control-DeepSeek/server && npm install && npm start → http://localhost:3000

What it does

dsh eventBoard effect
session/createdTask created (IN_PROGRESS, assigned to the harness agent)
user/message, assistant/messageActivity log excerpts
tool/call, tool/resultActivity log entries (tool name; error code on failure)
turn/endcompletedTask → REVIEW (humans approve to DONE)
turn/endblocked / failedTask → BLOCKED, structured error logged
turn/endaborted / interruptedTask → ASSIGNED
session/flushAwaited bounded flush of the plugin's HTTP queue

All Mission Control calls go through a serialized retry queue — an unreachable board never blocks the dsh agent loop.

Configuration

Override the bundle defaults per profile by addressing row id mission-control in the profile's cordis.patch.yml:

- id: mission-control
  config:
    missionControlUrl: http://localhost:3000
    agentId: agent-dsh          # must match ^[a-zA-Z0-9-_]+$
    agentName: DeepSeek Harness
    authToken: null             # or set env MC_AGENT_TOKEN
    maxExcerpt: 280             # max chars of content forwarded to logs
    flushTimeoutMs: 10000       # bound for the awaited session/flush drain
    events: {}                  # override dsh event names after upstream renames

Troubleshooting

  • Nothing on the board — confirm the server is up (curl $MISSION_CONTROL_URL/api/metrics) and check dsh logs for [mission-control] lines. Set dryRun: true in the row config to print payloads instead of sending.
  • Unknown event warnings after a dsh upgrade — map the renamed events via the events config block.
  • Auth failures (401/403) — set the same token in the server env (MC_AGENT_TOKEN) and the plugin (authToken or env).

License

MIT — part of JARVIS-Mission-Control-DeepSeek.