dsh-dashboard: Multi-Provider Task Orchestrator and Native Operations Dashboard for DeepSeek Harness

dsh-dashboard is a Symphony-inspired multi-provider task orchestrator and native operations dashboard plugin (DSH plugin) for DeepSeek Harness, maintained by Uddoo under the MIT license, written in TypeScript. It addresses the challenge of orchestrating tasks from Linear, GitHub, Jira, Asana, GitLab, and local sources within the native Harness environment, converting each task into an isolated Harness Agent run while preserving the native shell, sidebar, sessions, tools, model selection, and permission system. Core capabilities include loading a WORKFLOW.md with YAML frontmatter and Liquid prompts, deterministic priority ordering, concurrency limits, lifecycle hooks, exponential backoff retries, a durable Project Catalog, and a native Dashboard interface.

What task sources and orchestration features does the dsh-dashboard DSH plugin support?

The plugin supports Linear project issues, GitHub repository issues (excluding pull requests), Jira Cloud project issues with enhanced JQL, Asana project tasks, GitLab project issues, and credential-free local tasks. Each task source corresponds to an adapter, and only one source is active at a time. The orchestrator applies deterministic priority ordering, required labels, global concurrency, and per-state concurrency limits. It creates a persistent workspace per task and runs configurable after_create, before_run, after_run, and before_remove lifecycle hooks. Failed runs are retried with bounded exponential backoff, and source state is rechecked before every dispatch.

How does dsh-dashboard integrate with the native DeepSeek Harness environment?

This DSH plugin runs tasks through native Harness Agents and continues the same Harness session up to the configured turn limit. It adds a Dashboard entry to the native sidebar, exposing Board, Runtime, Projects, and Configuration views that show task state, session, workspace, turns, tokens, Agent events, retries, blockers, registered projects, and credential health. A durable Project Catalog is maintained in Harness storage; projects can be registered explicitly or discovered within bounded roots, but scanned candidates are never registered without confirmation.

How does dsh-dashboard handle projects, repositories, and credential security?

Projects are modeled separately from their Git repositories: Git projects use a worktree workspace strategy, while non-Git projects use controlled directories, and autonomous task claims remain off. External credentials stay on the trusted Host; credential values never enter Dashboard RPC payloads or browser state. The Local source provides Linear-style + controls for create, edit, state, priority, description, and delete operations, backed by an atomic Host-side JSON store.

How do I install dsh-dashboard?

To install this DSH plugin, use the following command:

dsh plugin --profile web add github:Uddoo/dsh-dashboard

After installation, the Dashboard entry appears in the Harness sidebar, and the Provider · Project control (e.g., Linear · ENG, GitHub · openai/example, Local · Personal) allows dynamic switching of task sources.

View more DSH plugins at dsh-plugin.org