@juuuw/autodsh
autodsh —— 基于 DeepSeek Harness 的自动化任务插件：触发器 + 自动化内容 + 结果通知，由任务面板统一管理。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add @juuuw/autodsh@0.2.0Autodsh 以 @juuuw/autodsh 发布，当前版本为 0.2.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
⚠️ AI Development Notice: This project was developed with AI assistance (DeepSeek Harness coding agent). Code, comments, and documentation contain AI-generated content, reviewed by humans and multiple automated review rounds. The publisher takes responsibility for the final content.
autodsh is an automation-task plugin for DeepSeek Harness. Users create automation tasks through conversation; each task follows a three-part architecture — trigger + automation content + result notification — managed from a unified task panel.
| Capability | Description |
|---|---|
| Persistence | Tasks and run history persist to $DSH_HOME/storages/autodsh.json (official storage-domain + JSON backend, atomic writes) |
| Lifecycle | The plugin starts/stops with DSH; enabled tasks resume scheduling automatically on startup |
| Triggers | Fixed interval, cron schedule, condition (last status / last duration / time window), parent-child |
| Execution isolation | Each task runs in its own agent session and working directory; child tasks inherit the parent's workspace and run context |
| Run statistics | Run count, total duration/tokens, last run time/status/result, used plugins and skills |
| Notifications | record (log) / email (SMTP, with file attachments) / session (DSH-IM social-software bridge) |
| Permission management | Per-task permission preset: workspace-write or danger-full-access (long-term authorization, no approval prompts) |
| Conversation control | 9 autodsh_* model tools: create/update/delete/list/detail/run/stop/history/settings |
| Auto-learning | Installs the autodsh-control skill so models automatically know how to control the plugin |
| Task panel | Built-in Web panel (list/detail/edit/run/stop/delete/history) with full configuration forms |
┌──────────────────────────────────────────────┐
Chat/User ─▶│ autodsh (Host half, resident with DSH) │
│ │
│ autodsh_* tools ←→ task store (storage-domain)│
│ │ ▲ │
│ ▼ │ change events │
│ trigger engine ──▶ task runner │
│ (interval/ (isolated agent session + │
│ cron/ workspace, stats) │
│ condition/ │
│ parent) │ │
│ ▼ │
│ notifier (log / email / IM) │
│ │ │
│ autodsh-control skill (model auto-learning) │
└───────┼──────────────────────────────────────┘
│ /autodsh/api (webServer routes)
┌───────▼──────────────────────────────────────┐
│ Task panel (Client half, Web settings page) │
└──────────────────────────────────────────────┘
See docs/ARCHITECTURE.md for details.
Requirements: DeepSeek Harness
>=0.1.2-rc.1(dsh 0.1.2 line) with@deepseek-ai/cordis ^4.0.2. v0.2.0 is not compatible with the 0.1.1 line — see RELEASE_NOTES.md.
Mount name must be the full package name. DSH Desktop 2.0.6 / dsh 0.1.2-rc.1 validate that a loader row's specifier equals the
namein the target directory'spackage.json. Install this package atnode_modules/@juuuw/autodshand mount it asname: '@juuuw/autodsh'. The legacy layout (node_modules/autodsh+name: 'autodsh') now aborts the whole DSH boot withdsh-plugin-desktop: profile package identity is invalid for autodsh;scripts/install-local.mjsmigrates it automatically.
# 1. Build in the project root
npm install
npm run build
# 2. Install into a target profile (copies artifacts, writes the scoped mount
# row, migrates a legacy unscoped install, backs up the patch)
node scripts/install-local.mjs desktop
# or: node scripts/install-local.mjs web
# 3. Restart DSH
Smoke-test the boot without touching your daily profiles (isolated DSH_HOME):
node scripts/verify-boot.mjs --app "<...>/DSH Desktop.exe"
# prints the plugin's own boot log; passes on "[ready] all ok"
Manual approach (when the install script does not apply):
dsh plugin --profile web add link:<absolute path of this repo>
# Add the mount row to the target profile's cordis.patch.yml:
- insert:
- id: autodsh
name: '@juuuw/autodsh'
Data lives in $DSH_HOME/storages/autodsh.json.
The package is published to the official npm registry as @juuuw/autodsh.
# 1. Install from the default npm registry
npm install @juuuw/autodsh
# 2. Add the mount row to the target profile's cordis.patch.yml:
# - insert:
# - id: autodsh
# name: '@juuuw/autodsh'
Alternative source:
@juuwaii/autodshis also published on the GitHub Packages registry (see README.zh.md for registry config).
After installing and restarting, just say:
The model auto-loads the autodsh-control skill and uses the autodsh_*
tools. You can also manage tasks in Settings → Autodsh Task Panel.
Name, description, enable toggle, trigger (type and parameters), task content (prompt), key parameters (sensitive ones masked), working directory, agent preset, permission preset, run timeout, notification channels/timing, email recipients, parent task, run statistics (last run time/duration/status/ result, totals, used plugins/skills), and run history.
The panel's Edit Config form supports:
workspace-write / danger-full-access)Each task can declare a permission preset (permission field, also available
in the panel and autodsh_task_create/update tools):
| Preset | Sandbox | Approval | Use case |
|---|---|---|---|
workspace-write | workspace + allowed temp dirs | ask | Default; wider operations require approval |
danger-full-access | full file access | never | Unattended long-running tasks: full permissions, no approval prompts |
The preset is applied to the task agent at run time via permissionPresets.set
(sandbox mode + approval policy). Unknown preset names only warn and do not
block the run.
<dataRoot>/notifications.log (JSONL); always available.smtp.host/port/secure/user/password/from
via the autodsh_task_settings tool (or settings), and set emailTo on the
task. A zero-dependency SMTP client (node:net/tls) supports 465 direct TLS,
587/25 STARTTLS, AUTH LOGIN/PLAIN, UTF-8 base64 bodies, and file
attachments (multipart/mixed; result files under 10 MB are attached
automatically).interval: fixed period in ms (optional random jitter);schedule: 5-field cron (min hour day month dow, local timezone; day/dow
combine with standard cron semantics);condition: last run status / last duration comparison / time window
(fires once per window);parent: triggers the child after the parent run ends, on
success | failure | completion | always (with optional delay), and injects
the parent's result summary into the child prompt.npm install
npm run build # Host (tsc) + Client (tsc + rollup)
npm test # unit tests (node --test)
.js suffix
convention.See README.zh.md for the full requirement mapping table.
$DSH_HOME and gitignored
directories.secret flag: masked as ****** in the
panel and model tools.$DSH_HOME/settings.yaml (DSH defaults to 0600) and are masked on read.