In DeepSeek Harness (DSH) engineering scenarios, an Agent needs to discover tasks within a project scope, assess the impact of changes, execute background tasks, and collect verification results. The dsh-project-ops plugin is designed to address these needs. It does not patch Harness source code or bypass approval workflows; instead, it provides bounded management and acknowledgment mechanisms for project tasks through Agent tools.

Plugin Positioning

The plugin is maintained by developer Missher12 under the MIT license. It is a standalone Cordis project execution plugin compatible with DeepSeek Harness 0.1.5-rc.2 / Cordis 4.0.2. Its core value lies in providing an Agent with a controlled environment for task discovery, planning, and execution, ensuring that tasks run within Harness’s existing Jobs runtime and sandbox rather than creating new engines or bypassing permissions.

Compatibility and Prerequisites

Before use, ensure the host environment satisfies the following version and configuration requirements:

  • DeepSeek Harness: 0.1.5-rc.2
  • Cordis: @deepseek-ai/cordis 4.0.2
  • Node.js: ^22.19.0 or >=24.0.0
  • Profile services: The current Profile must provide the fs, tools, jobs, and systemPrompt services.

Installation and Enablement

In the Web Profile environment, use the following command to install the plugin package:

dsh plugin --profile web add https://github.com/Missher12/Missher-DSH-Project-Ops/releases/download/v0.3.1/dsh-project-ops-0.3.1.tgz

After installation, ensure that the Profile has been reloaded. Note that code updates in the Git repository do not automatically replace the locally installed plugin. To update, manually rerun the installation command above.

Core Capabilities and Tools

After successful installation, the Agent can use the following four main tools for task management:

  1. missher_project_ops_task_list

    • Purpose: List project tasks.
    • Behavior: Discovers tasks from the root directory of the current session and declared package workspaces. The returned results include task identity, source manifest, SHA-256 checksum, relative workspace, optional package name, inferred purpose, dependent task IDs, and run status. This tool does not return specific task command text.

  2. missher_project_ops_task_plan

    • Purpose: Task planning and impact analysis.
    • Behavior: Accepts changedFiles for 1 to 256 relative workspaces and a target (verify / build / all). It identifies directly affected packages, reverse dependencies, task dependencies, and matching root tasks, then returns a stable topological sort, affected workspace names, diagnostics, and a summary based on project content and snapshots.

  3. missher_project_ops_task_run

    • Purpose: Background task execution.
    • Behavior: Accepts a task ID, manifest checksum, and optional mode (foreground / background / auto). It executes the task through Harness’s Jobs runtime and returns an execution acknowledgment.

  4. missher_project_ops_verification_gate

    • Purpose: Verification acknowledgment collection.
    • Behavior: Collects and evaluates verification results after task execution.

Notes

  • Permissions and boundaries: The plugin reuses the host’s command permissions and sandbox, and does not create new shells or job registries. It does not bypass approval workflows.
  • Environment isolation: The plugin runs with the permissions of the current Profile, so the source code and license should be carefully reviewed before installation.
  • Agent workflow: The Agent should follow a fixed workflow: first list tasks, then plan based on changed files, and finally run only the returned task declarations and collect acknowledgments.