Skip to content

titanwings/dsh-automation

323Last commit Aug 14, 2026

dsh-automation DSH plugin

dsh-automation is a DeepSeek Harness Web plugin for creating and managing one-shot or recurring coding automations. Each occurrence runs a saved task in a fresh root Agent and Session, with captured workspace and permission settings, plus retained run records.

How to install the dsh-automation DSH plugin

dsh plugin --profile web add github:titanwings/dsh-automation#v0.1.5

Copying does not run this command. Review the repository and version before use.

Data source

Snapshot date: Aug 15, 2026

manifest-valid

What the dsh-automation DSH plugin can do

  • Creates one-shot, interval, daily, and weekly task schedules.
  • Manages automations from the DSH Web Automations tab or six Agent tools.
  • Runs every occurrence in a fresh root Agent and Session rather than inheriting source-chat history.
  • Captures workspace, working directory, Agent preset, model target, and permission preset for runs.
  • Provides run states, revision snapshots, summaries, structured errors, and result Session IDs.
  • Supports read-only and workspace-write permission modes.
  • Applies scheduling controls including overlap prevention, recovery grace windows, timeouts, and at-most-once dispatch policy.

Where the dsh-automation DSH plugin fits

  • Run weekday regression triage against local test evidence.
  • Generate recurring repository health reports.
  • Schedule a later one-shot verification of a flaky failure.
  • Refresh known generated code and run focused checks.
  • Execute a bounded maintenance task in a workspace-write window.

Who the dsh-automation DSH plugin is for

  • DeepSeek Harness users who need recurring or delayed coding tasks.
  • Developers managing repeatable workspace-scoped maintenance and verification work.
  • Teams that need inspectable records of unattended Agent runs.

dsh-automation DSH plugin limitations

  • The DSH Host must be running for tasks to start; version 0.1 is not an operating-system daemon.
  • Only local execution is implemented; multiple Hosts are not coordinated through one storage directory.
  • Schedules cannot use raw cron, arbitrary shell actions, multi-workspace targets, DAGs, or hidden cross-run memory.
  • Unattended danger-full-access is not accepted; supported modes are read-only and workspace-write.
  • Runs are not automatically retried after possible side effects, and external side effects are not guaranteed exactly once.
  • Tasks do not inherit the creating conversation’s history, inbox, grants, or past approvals.

Objective checks

These signals come from public metadata scans. They are not a security certification.

  • dependency counts

    package.json declares 2 runtime, 7 development, 1 peer, and 0 optional dependencies.

    info
  • dsh bundle declared

    package.json declares DSH bundle metadata.

    info
  • license declared

    GitHub reports the repository license as MIT.

    info
  • package manifest available

    A root package.json was captured and can be inspected by the registry.

    info
  • source available

    Public GitHub source metadata is available for this registry snapshot.

    info

dsh-automation DSH plugin alternatives

dsh-automation DSH plugin questions

What is the dsh-automation DSH plugin?

dsh-automation is a project included in the current DSH plugin snapshot. This page organizes repository metadata and reviewed notes, but you should still inspect the upstream repository before running it.

How do I install the dsh-automation DSH plugin?

The page shows the install command captured from the source record. Copying does not run it, so confirm the package, profile, and version against upstream documentation first.

Which DSH profile does dsh-automation use?

The snapshot records web as the dsh-automation profile. DSH conventions can change quickly, so verify the manifest and README before installation.

Is dsh-automation compatible with the current DSH release?

The source data does not include a verified compatibility matrix. Check recent commits, releases, and DSH breaking changes, then test in a profile you can roll back.

What should I do if dsh-automation fails to load?

Check the install command, selected profile, dependency logs, and Cordis startup output first. Keep the exact error string, then compare it with this site's fix pages and upstream issues.

What are the closest alternatives to dsh-automation?

Related plugins on this page come from the current snapshot and are only candidates. Compare capabilities, maintenance activity, installation method, and limitations before choosing one.