DeepSeek Harness Plugin

alpacachen/dsh-kanban

Stars ★ 25 Downloads (30d) 4,449 Category Workflow & Automation Added 2026-08-21 npm @alpacachen/dsh-kanban

Human-led Kanban and AI-run workflows in one DSH plugin. Manage workspace tasks together with agents using draggable cards, search, priorities, labels, due dates, Markdown, images and comments. Create and edit reusable workflows through chat, configure stage models, and let AI execute each stage with DSH tools and permissions. Follow progress on a flowchart, inspect native stage conversations, approve results or send them back with feedback, and retry failed stages or terminate tasks. Preview files in each task's own artifact directory and use execution history and review feedback to improve workflows for future tasks.

Install

# from npm (prebuilt)

dsh plugin --profile web add @alpacachen/dsh-kanban

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:alpacachen/dsh-kanban

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

README

One plugin, two ways to work. Use Kanban to organize tasks and decide what happens next. Use Workflow to give AI a repeatable sequence, follow its execution, and step in at review points.

Both live under Kanban · Workflow in the sidebar. Switch modes beside the workspace name; the plugin remembers your last mode and workspace.

Kanban · Work you lead Workflow · Work AI runs
Start with A task or a plan from a conversation A reusable process designed with your Agent
Move forward You or your Agent update cards Create tasks manually or on a schedule. AI runs the stages in order.
Keep control Priorities, deadlines and review columns Human approval, feedback, retry and stop
Keep the context Descriptions, screenshots, comments and activity Stage conversations, reports and task-specific files

Get started

Version 1.13.1 requires DSH 0.2.2-rc.5 and supports desktop and Web. For Workflow, configure an execution model in DSH first.

For DSH 0.2.2-rc.3, install @alpacachen/dsh-kanban@1.13.0.

Desktop — Open Plugins, add @alpacachen/dsh-kanban, and enable it.

Web — Install the plugin, then restart your Web instance to load it:

dsh plugin --profile web add @alpacachen/dsh-kanban

Open Kanban · Workflow in the sidebar and choose a workspace. Stay in Kanban to create your first card, or switch to Workflow, choose Create in chat, and describe a process.

Kanban — Work you lead

Turn plans into visible tasks. Move cards yourself, ask your Agent to keep them up to date, and take the next step when you are ready.

Kanban board with task search, priority and label filters, and four task columns

Actual plugin UI with isolated example data. Each workspace has its own board.

  • Plan together. Ask your Agent to break down a goal, write acceptance criteria and create cards with 19 built-in board tools.
  • Find the next task. Search titles, descriptions, comments and IDs; combine priorities, labels and due-date filters.
  • Keep evidence close. Add Markdown, screenshots, comments and activity history to a card.
  • Continue in chat. Bring a card and its saved images into a new conversation as an editable draft, ready for you to send.

Try asking your Agent:

Break phone sign-in into testable tasks. Check existing cards first to avoid duplicates. Add implementation steps and acceptance criteria, and mark launch blockers as P0.

Kanban guide → · All 19 board tools →

Workflow — Work AI runs

Describe a process once, then give it new inputs. AI runs its stages using DSH's normal tools and authorization; you can follow the work and decide at human review points.

An example process. Human review pauses execution until you approve, return it with feedback, or stop.

Design it in conversation

Ask your Agent to create or revise a workflow. It saves the stages, instructions, deliverables and review points. New AI stages inherit the model used in that conversation; you can later edit stage instructions and choose a model and reasoning effort in the stage dialog.

Create a reusable research workflow: read the materials, draft a report with sources and open questions, wait for my review, then finalize the report. If I return it, go back to drafting. Save the workflow without running a task.

Run it with a new input

Expand a workflow in the home list and choose Create task. Enter what you need and send it. No separate task name or model setup is required.

  • See the work. The diagram highlights the current stage. Click a stage to inspect its native DSH conversation, available reasoning text, tool calls and replies.
  • Review and revise. Approve to continue or return with feedback. Earlier reports and review decisions remain available.
  • Keep files separate. Every task has its own output directory, shared by its stages. Preview files in place, open the directory, or delete deliverables with confirmation.
  • Resume deliberately. Retry a failed stage after checking the cause. After a crash, reconcile the old execution before retrying; completed upstream stages are retained.

Schedule task creation

Open a workflow and click the Schedule clock icon in the top right. Each workflow can have one schedule that runs once, daily, or on selected days of the week. Saving activates it in the time zone shown in the dialog.

At each scheduled time, the DSH Host creates and queues a regular task using the latest saved workflow definition. The task list shows its scheduled time. The same execution and human review steps apply.

The schedule works with the page closed while the DSH Host is running. Occurrences missed while the host is offline are skipped. Choose Remove schedule to stop future triggers. Existing tasks continue as usual.

Improve the process from its history

Choose Optimize from history to start a conversation with an analysis prompt. The Agent can inspect previous task results, review feedback, stage conversations and recorded timings. Changes apply to future tasks; existing tasks keep their original workflow version.

Workflow guide → · Agent interface (中文) → · Validation and recovery boundaries (中文) →

What to expect

  • Native DSH execution. Workflow adds orchestration and human review, with no separate tool-permission system or extra model-turn, tool-call or stage-time budgets.
  • Sequential stages. Stages in a task run in order. Tool concurrency and model-request retries follow DSH; a failed workflow stage is retried by you.
  • Small handoffs. Stages receive upstream conclusions, evidence references and a file index. Full reports are read when needed instead of carrying the entire conversation forward.
  • Review scope is explicit. Approval applies to the saved stage reports. It does not snapshot project files or undo changes made by tools.
  • Two interface languages. Controls, owned error messages and dates follow DSH's Chinese or English setting. Your inputs, prompts and saved outputs retain their original language.

If DSH is forcibly killed, previously launched commands can survive on macOS. Check that old commands and external operations have stopped before confirming recovery. The plugin will not silently rerun an interrupted stage.

Documentation

You want to… Read
Use cards, search, images and chat handoff Kanban guide
Create, schedule, review and improve workflows Workflow guide
Understand board tools Board tool reference
Back up your data Kanban data · Workflow data
Build and validate the plugin Development checks · Workflow acceptance record
Report a problem or suggest a change GitHub Issues

MIT · Built for DeepSeek Harness

Content from the project README on GitHub ↗

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.