DeepSeek Harness focuses on conversational and chat interactions, excels at reasoning, but is weak at long-term maintaining operational truth. The dsh-codex-kanban plugin provides Harness with a persistent visual kanban board. It does not build a standalone chat interface; instead, it uses native tools to let Harness chat read and update cards, while integrating Codex as the official subagent.

Plugin Overview

  • Name: dsh-codex-kanban
  • Author: sonozaki7
  • Category: Workflow
  • License: MIT

This plugin stores cards in local JSON files rather than browser storage. It integrates the official Codex subagent, provides tool-based operation interfaces, and supports state transitions, evidence tracking, local execution, and secure binding.

Installation and Prerequisites

Before installation, ensure the following environment requirements are met:
* Node.js version >= 22.19
* Authenticated Codex CLI
* DeepSeek Harness environment

Only administrators need to run the installation command once. After installation is complete, restart the DSH web profile.

dsh plugin --profile web add github:sonozaki7/dsh-codex-kanban

Core Features

State Transition Management

The plugin explicitly defines task state transition paths:
* backlog: worth remembering but not ready to start.
* ready: context and acceptance criteria are sufficient.
* running: a person or agent is actively working on it.
* review: work is completed but not accepted (evidence required).
* done: criteria are met and evidence is present.
* blocked: a specific blocker exists; enter this state with a reason.

Tool-Based Operations

The plugin registers the following tools with the DeepSeek agent:
* kanban: supports list, create, update, move, evidence, delete.
* kanban_codex: delegates an existing task to the Codex subagent for execution.

Important fields include project, status, owner, acceptance_criteria, blocked_by, evidence_text, and evidence_url.

Evidence and Security

  • Evidence tracking: acceptance criteria, blockers, execution reports, and validation evidence are all stored on the card.
  • Local execution: the dashboard is bound to 127.0.0.1:4317, and data is written to the local file ~/.dsh/codex-kanban/board.json.
  • Permission control: the data file can only be written by the owner, and unauthorized modifications from external browsers are rejected.

Usage Workflow

After installation, day-to-day usage is primarily visual:

  1. Open the workbench: visit http://127.0.0.1:4317 in your browser.
  2. Create a card: select “Create my first card”, then describe the expected outcome and acceptance criteria.
  3. Prepare the work: move the card to the Ready state.
  4. Forward the task: click the “Open in Harness” button on the card. The plugin copies the card’s structured task message and opens the official Harness UI.
  5. Execute the task: paste and send the prepared message in Harness. DeepSeek can update the same card and, when appropriate, use Codex internally to execute code.

Notes

  • Codex execution results: After Codex work is complete, the status defaults to review rather than done. The status can only transition to done after being reviewed by a person or agent and evidence is attached.
  • Dependencies: The plugin depends on @deepseek-ai/dsh-subagent-codex and @deepseek-ai/schemastery.
  • Operation modes: Desktop supports card dragging; mobile or keyboard operation uses the status menu at the bottom of the card.

Ecosystem Context

The DeepSeek Harness philosophy is “everything is a plugin.” This plugin runs locally and does not rely on cloud task services to expose project context. It is suitable for scenarios where you need to switch among multiple repositories and AI chats, and want DeepSeek to coordinate while Codex handles boundary code tasks.

GitHub Repository | Plugin Catalog