Preface

DeepSeek Harness (DSH) adopts a modular plugin architecture. Existing workflows usually rely on folders and sessions, but lack a “project” concept that aggregates them. The dsh-project plugin integrates multiple folders, multiple sessions, and shared memory/instructions into a single project entity, acting as an overlay to fill this missing concept.

Plugin Overview

The plugin is maintained by lanyun077 and is licensed under the MIT License. It functions as an overlay, introducing the “project” concept without modifying the DSH core.

Core Features

  • Project tree and organization: The sidebar displays a “Project” entry, showing a project tree (project → folder → session). A project can attach multiple folders, each of which is automatically registered as a workspace. Sessions can be dragged into or moved out of folders.
  • Session management: Supports creating a new session with one click in any folder of the project, implemented by reusing workspaces.connectWorkspace.
  • Shared memory: The project-level PROJECT.md serves as shared memory and is injected as a whole when each session starts. Agents can append memory using the project_memory_write tool or read an overview using the project_context tool.
  • Project instructions: The project-level AGENTS.md is injected into the system-prompt section of every session and supports hot reloading.

Installation and Enablement

This is a local plugin and must follow DSH’s plugin loading conventions.

  1. Make dsh-project resolvable by the profile (for example, as a file:../dsh-project dependency, or via a node_modules symlink).
  2. Add the following configuration to the profile’s cordis.patch.yml:
- insert:
    - id: project
      name: 'dsh-project'
  1. Restart DSH web (dsh web).

Typical Usage

  • Click “New” in any folder within the project to create a session associated with that project.
  • Reuse workspaces.connectWorkspace to create sessions.
  • Manage the project.json, AGENTS.md, and PROJECT.md files under the ~/.dsh/projects/<id>/ directory.
  • Append project memory using the project_memory_write tool, or read an overview using the project_context tool.

Applicable Scenarios and Notes

  • Explicit ownership: A session must explicitly belong to a project (created or added through the “Project” panel). The plugin does not automatically infer project ownership from the directory.
  • Memory mechanism: PROJECT.md is currently injected as a whole (without vector retrieval), so it should be kept concise. Structured retrieval is planned for v2.
  • Version limitations: v1 does not include project-level MCP/skills/default model/cross-session subtask dispatch.

Summary

dsh-project provides a missing project-level abstraction in the DSH ecosystem. By managing resources through a tree structure and using PROJECT.md and AGENTS.md to unify context and instructions, it helps maintain complex Agent workflows. The complete documentation and source code are available on GitHub.