deepseekplugins

DeepSeek Harness plugin

JARVIS-Mission-Control-DeepSeek

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

Tools & Capabilities
Jump to install

Source facts

Repository
Asif2BD/JARVIS-Mission-Control-DeepSeek
Latest update
Aug 20, 2026
Category
Tools & Capabilities
GitHub stars
1
Format
plugin
Package path
integrations/deepseek-harness/dsh-plugin-mission-control
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
integrations/deepseek-harness/dsh-plugin-mission-control/package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-21

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/Asif2BD/JARVIS-Mission-Control-DeepSeek/tree/HEAD/integrations/deepseek-harness/dsh-plugin-mission-control
Plugin: JARVIS-Mission-Control-DeepSeek
Author: Asif2BD

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer2 files
README.mdSource · read only

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/end → completedTask → REVIEW (humans approve to DONE)
turn/end → blocked / failedTask → BLOCKED, structured error logged
turn/end → aborted / 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.

Back to searchOpen GitHub repository

More related plugins

View category