Foreword

DeepSeek Harness (DSH) captures execution traces of code work: every retrieval, tool call, and retry is recorded as a structured event, because the executor emits those events rather than because someone remembers to log them. Content production currently lacks this kind of logging. A task board can only tell you that a draft went from todo to in_review, but not which twenty articles the outline was extracted from, how long the second revision took, or the editor’s specific reasons for rejection. MetaBoard aims to bring this trace capability to non-code work, starting with content production.

Plugin Introduction

MetaBoard is a plugin for DeepSeek Harness (DSH). It starts with content production and establishes execution traces for non-code work.

  • Positioning: Provides execution trace logging for non-code work (such as content production).
  • Maintainer: SilasSolivagus
  • License: MIT
  • Current status: Phase 1 (standalone dsh plugin form) has been implemented. Two acceptance items remain open (full end-to-end loop validation and concurrent conflict validation against a real runtime).

Core Features

MetaBoard provides two interface sets: CLI commands and DSH tools, for work item management and trace recording. It follows the design principle of “no fork, no host modification, and no new event types.”

  • CLI commands: Used to manage work items directly, including creation, approval, listing, viewing, status updates, comments, rejection, renaming, archiving, setting projects, and project management operations.
  • DSH tools: Invoked by the Agent during conversation to create work items, record research materials, drafts, revisions, reviews, read work items, and generate reports.
  • Architecture constraints: Do not modify the DSH host and do not introduce new event types.

Installation and Enabling

The plugin is currently in the Phase 1 implementation stage. If you are looking for something to install today, it is best to come back later. The plugin depends on a Node.js environment, with version requirement >=22.5.

Typical Usage

MetaBoard offers two usage methods: CLI and Agent tools.

CLI examples:

  1. Create an idea: Record an idea and place it into the todo queue.
    metaboard new <title> [--project <pid>]
  1. View the board: List approved work items, grouped by status.
    metaboard ls [--project <pid>] [--all]
  1. View details: Display the full timeline of a work item, including board operations and DSH session events.
    metaboard show <id>
  1. Diagnose: Check whether work item logs, project logs, and the DSH session store are reachable.
    metaboard doctor

DSH tool examples:

During a conversation, the Agent can invoke the following tools:
* metaboard_work_create: Record a new work item.
* metaboard_research: Record collected source materials.
* metaboard_draft: Record a written draft.
* metaboard_review: Record human review decisions.

Use Cases and Cautions

  • Use cases: Workflows that need to track the origins, version changes, and review history of non-code work (especially content production).
  • Notes: Two acceptance items are still incomplete; full end-to-end loop validation and real concurrent conflict validation are required.
  • Permissions and security: The plugin runs with the permissions of the current DSH process. Review the source code and license (MIT) before use.

Short Closing

MetaBoard extends the trace capability of code work to content production by reusing the DSH conversation node assembler, enabling an inspectable record of the work process. See the links below for related directories and source code.