DSH Market
D

Dsh Automation

by titanwings · titanwings/dsh-automation

Build failsBundlegit (build fails)fresh

DSH 自动化插件:让 Coding 任务按计划在全新 Agent Session 中运行,并由用户或 Agent 创建和管理定时任务。 / Run coding tasks in fresh Agent sessions and manage schedules from DSH Web or an Agent.

Install Dsh Automation

Likely fails to load: not on npm, needs a build, and ships no `prepare` script — a git install fetches sources, not built artifacts, so the entry point is never produced.

This install is expected to fail

A git install pulls source, not build output. This package needs a build step, has no prepare script to run it, and is not published to npm — so nothing produces the compiled output the loader then goes looking for.

Three things would fix it, all of them on the author's side: publish the package to npm, add a prepare script that builds on install, or commit the build output to the repository. Until one of those happens, the command below is here so you can reproduce the failure, not so you can install it.

What would be run — expected to install and then fail to load

# 1. add the bundle to a profile — --profile my-profile points at $DSH_HOME/profiles/my-profile
dsh plugin --profile my-profile add github:titanwings/dsh-automation

# 2. verify: the bundle should show up as a layer in the resolved config
dsh --profile my-profile --dump-config

# 3. boot the profile
dsh --profile my-profile

Before you run it

  • A plugin runs with your permissions once loaded: it can read your files, use your credentials and reach the network. Tool approvals do not sandbox it.
  • Installing from git resolves a moving branch. Pin a commit — github:titanwings/dsh-automation#<commit-sha> — so the code you reviewed is the code you install.

Prerequisites

API key
Not required.
Network access
Not required at runtime.
Language
TypeScript — a git install pulls this source, not build output.

Install check

Every field the verdict was derived from, so you can re-derive it yourself

Field checkedResultWeightWhat the spec says about it
lifecycleScriptspassinfono install-time scripts
dsh.bundlepassfatalpackage.json declares a `dsh.bundle` layer
dsh.bundle.patch filepassfatalpatch file present at `cordis.patch.yml`
npm registrymissingwarn`@dsh-external/dsh-automation` is not published to npm
prepare scriptmissingfatalneeds a build but ships no `prepare` script — a git install fetches sources, not built artifacts
Verdict reason
git-only + needs build + no prepare script
package.json read
package.json
Rules applied from
docs/user/develop/basic/publish.md
Checked at
2026-08-15

From the README

Excerpt as published by the author, plain text, unedited

🕒 Need recurring or one-shot coding work to run later without relying on an old chat? 🧭 Need each unattended run to stay inside an explicit workspace and permission boundary? 🧾 Need to inspect what ran, which revision it used, and how it ended? Create and manage schedules from DSH Web or any eligible root Agent. Every dispatched occurrence starts in a fresh root Agent and Session, then leaves an auditable record. **Self-contained task + schedule + permission boundary → fresh root Agent + fresh Session + durable run history** **English** · [简体中文](README.zh-CN.md) DSH Core Schedule is the right tool for reminders in the current conversation: “come back to this Session in ten minutes.” `dsh-automation` handles a different job: “run this complete task independently

Topics

GitHub topics on this repository

More in Coding Agent Cli Review

Ranked by similarity inside the cluster, not alphabetically