In the development and operations of DeepSeek Harness (DSH) agents, long-running background tasks (such as Windows Scheduled Tasks or KAi cron) often lack a visual monitoring entry point. Besides checking status from the command line, there is no intuitive dashboard for uniformly managing the scheduling, dependency scripts, and health status of these carriers. The amoss-1/routine-taskboard plugin is designed for this purpose. It turns the DSH Web GUI sidebar into a “Routine Taskboard,” providing a one-stop management interface for these long-lived tasks.
Plugin Positioning¶
This plugin is maintained by Amoss-1 and is part of the DeepSeek Harness plugin ecosystem. It focuses on displaying scheduled tasks, script steps, and health indicators in the Web interface. Since v0.1.9, the plugin is fully self-contained and no longer depends on the official dsh-taskboard plugin or its /dsh-taskboard/state API.
Core Features¶
- Board View: Click “Routine Taskboard” in the DSH Web sidebar to switch the conversation column to a board-style view. Each long-lived scheduled task is rendered as a row, including the schedule name, time, carrier, dependency scripts, input/output files, and health indicator.
- Script Steps and Execution: Supports tasks with multiple scripts displayed as numbered steps (1. 2. 3.). Each step can be clicked and located in the file explorer, and can also be run separately by clicking ▶. Supported script extensions include py/ps1/bat/vbs/mjs.
- Status Operations: For Windows Scheduled Task carriers, row-level action buttons are provided. Button states change with task status: while running, “Start” and “Disable” are shown; when disabled, only “Re-enable” is shown.
- Health Indication: Status is shown with a three-color indicator: running (green), disabled (amber), and abnormal (red).
Installation and Enablement¶
- Run the installation command in the terminal:
dsh plugin --profile web add routine-taskboard
- Restart the
dsh webservice. - A “Routine Taskboard” entry will appear in the sidebar. Click it to switch views in the conversation column.
Configuration and Data¶
- Fixtures Registry: The plugin reads task card data from
$DSH_HOME/storages/routine-taskboard.json(including id, name, scripts, input, output, healthKey, status, etc.). The file is an empty array by default; cards must be registered via the host API or by editing the file directly. - User Configuration File: Machine-specific path mappings and curated mappings are stored in
$DSH_HOME/storages/routine-taskboard.config.json. This file is not overwritten during plugin upgrades, making it suitable for business paths and script mappings. - Fallback Mechanism: If no configuration file is present, the plugin extracts paths using regular expressions by default. The file path for the business health ledger can be specified via the environment variable
RTB_PIPELINE_FILE.
Interface Description¶
The plugin provides data access and operations through the following host routes:
| Route | Method | Function |
|---|---|---|
/routine-taskboard/fixtures |
GET | Get taskboard data |
/routine-taskboard/pipeline |
GET | Get business health ledger content |
/routine-taskboard/config |
GET | Get user configuration |
/routine-taskboard/open |
POST | Open the specified path in the file explorer |
/routine-taskboard/run |
POST | Execute schtasks /Run |
/routine-taskboard/state |
POST | Change task status (/DISABLE or /ENABLE) |
/routine-taskboard/run-script |
POST | Run a single script in the background |
Notes¶
- Since v0.1.9, the plugin is fully self-contained and does not depend on the official
dsh-taskboard. - During plugin upgrades, the user configuration file (
.config.json) and fixtures registry (.json) are not overwritten. - The plugin runs with the privileges of the DSH process. Please review the source code and license before installation.
Summary¶
Routine Taskboard reduces the maintenance cost of long-running background tasks by providing a visual row view and script operation capabilities. To learn more or contribute code, visit the GitHub repository.