usersx/dsh-automation-center

DSH Automation Center

中文 | English

The hero is project artwork, not a product screenshot. Every functional screenshot uses the original official DeepSeek skin on DSH 0.1.0-rc.8.

DSH Automation Center adds scheduled, auditable Agent runs to DeepSeek Harness. Every occurrence creates a fresh root Agent and Result Session in the selected Workspace. The center owns definitions, schedules, permissions and run history; the Result Session retains the complete output and trajectory.

The same package selects the deepest native surface available, without DOM injection or Sidebar replacement:

• Stock compatibility mode: unmodified DSH from 0.1.0-rc.8 through the current 0.1.2-alpha.2 exposes a global Settings → Automations section that works without a Session; the Automation Conversation tab remains a shortcut. No Shell Page Patch is required.
• Global center mode: when DSH exposes sidebar.primary.action and shell.page, the plugin automatically moves to a root action below New Session and above Workspaces.

Current version: 0.1.0-alpha.8. Compatibility validation is not a security audit.

Install Alpha.8 from GitHub Releases

Download dsh-automation-center-0.1.0-alpha.8.tgz, then install it from the download directory.

dsh plugin --profile web add ./dsh-automation-center-0.1.0-alpha.8.tgz

Desktop profile:

dsh plugin --profile desktop add ./dsh-automation-center-0.1.0-alpha.8.tgz

The Release also provides a SHA-256 file, SPDX SBOM, and GitHub/Sigstore build attestation. npm publication is complete only after fixed-version, integrity, and provenance registry readback; a GitHub Release or workflow approval is not sufficient evidence.

Fully quit and reopen DSH after installation. Use Node.js ^22.19.0 or >=24.0.0. Remove or disable @dsh-external/dsh-automation; when both schedulers are present, this plugin reports AUTOMATION_PLUGIN_CONFLICT instead of scheduling twice.

Capabilities

• Cross-workspace overview, filtering, statistics and recent runs.
• One-time, fixed-interval, daily and weekly schedules with explicit IANA time zones.
• Create, edit, pause, resume, delete, run-now and cancel flows.
• A fresh root Agent and Session for every occurrence; chat sessions are never reused.
• Result Session titles derived from the automation task rather than the project.
• Read-only and workspace-write unattended policies.
• Per-automation model policy: inherit the live DSH default, or pin provider, model and reasoning effort; every Run records the effective model.
• Workspace, preset and model preflight exposes blocked definitions before a useless Session is created.
• Idempotent commands, overlap protection, deterministic claims, bounded misfire handling and conservative restart recovery.
• Supervisor phases, lease heartbeats and a whole-job deadline covering preflight through delivery.
• Derived expected/admitted/claimed/queue/progress health plus structured Outcome/Attention, attempts and side-effect uncertainty.
• Optional isolated Git worktree review with clean-base enforcement, patch hash/stat, and accept/keep/discard actions.
• Lifecycle events carry runId/revision/sequence; the model sees only tools allowed by the effective unattended policy.
• Every Run exposes a stable identity derived from Definition revision, occurrence, and Workspace scope rather than list position or a dynamic node name.
• Host, storage, and Git review cleanup retain an owner until asynchronous settling completes; interrupted accept/discard actions reconcile after restart.
• Durable write receipts with request ID, revision and committed | rejected | unknown outcomes, followed by an authoritative Client read.
• Durable history, summaries, Result Session links, effective model and structured error codes.
• Read-only migration from legacy dsh_automation v1 data.

Original DeepSeek UI

Every functional screenshot uses the original DeepSeek skin.

Stock rc.8 compatibility mode (dark)

Unmodified rc.8 exposes Automation beside Conversation and Trajectory. The screenshot also shows a task card, a structured failed run and clearance above the Session composer.

The following three screenshots show global center mode when both Shell slots are available.

Root action aligned with New Session

Global center

Create an automation

Architecture

DSH Surface Adapter
  ├─ stock 0.1.0-rc.8 → 0.1.2-alpha.2: settings.section + conversation.view shortcut
  └─ enhanced: sidebar.primary.action + shell.page
                         │
                         ▼
Automation Center ──RPC──▶ AutomationEngine ──▶ Definitions / Runs
                                        │
                                        ▼
                              Fresh Agent + Session
                                        │
                                        ▼
                              Result Session + audit

The Host-side AutomationEngine is the deep module. Both Client adapters, authenticated RPC, scheduler and Agent tools share its snapshot / dispatch boundary instead of accessing storage directly.

Compatibility

As of 0.1.2-alpha.2, stock DSH still has no sidebar.primary.action or shell.page, so a plugin cannot add a true Sidebar root action through public APIs. It can still provide global management through the native settings.section. This project deliberately avoids a brittle DOM-injection imitation. Once the generic Shell slots land upstream, the same npm package enables Sidebar global-center mode automatically.

See the exact alpha.8 acceptance results, including blocked and unrun cases. The alpha.7, alpha.6 and alpha.5 records remain historical observed baselines.

Safety boundaries

• Management RPC uses rc.8/rc.2 loopback authority and alpha.1/alpha.2 authenticated one-time-token channels; workspace/profile scope remains mandatory.
• UI input accepts registered Workspace IDs, never arbitrary host paths.
• Automation Agents cannot create more automations or wait for interactive approval.
• Unattended tools are allowlisted and background-process escape is rejected.
• Restart does not blindly replay an interrupted run that may already have side effects.
• Logs and RPC errors must not expose prompts, tokens, environment variables or credentials.
• Cancellation cannot roll back completed side effects.

Development and release evidence

pnpm install
pnpm check

CI runs typecheck, tests, build and repository validation on Linux, macOS and Windows, then installs the tarball into isolated unmodified DSH 0.1.0-rc.8, 0.1.1-rc.2, 0.1.2-alpha.1, and 0.1.2-alpha.2 profiles. The release workflow attaches a fixed tarball, SHA-256, SPDX SBOM, and GitHub/Sigstore build attestation; npm publication is complete only after workflow and registry readback.

Documentation

• Acceptance criteria (Chinese)
• Alpha.8 acceptance results
• Technical design (Chinese)
• Release process
• Changelog
• Contributing
• Security policy
• Roadmap
• Third-party notices

Known limitations

• Stock DSH 0.1.2-alpha.2 provides global management in Settings; a Sidebar root action still requires the two generic upstream slots.
• The 0.1.2-alpha.2 Web Alpha.8 candidate passes install, activation, RPC, direct/worktree failure paths, Result Session, and ghost-Session negative checks; a successful real-model Run was not run. The macOS Desktop 2.0.3 Alpha.7 real-model Run and three cold starts remain historical evidence.
• The first release has no distributed scheduler, remote workers or cloud credential vault.
• Cancellation cannot undo file changes or external calls that already occurred.
• This remains an Alpha; stable release gates are defined in the acceptance documents.
• DSH 0.1.2-alpha.2 cannot yet prove wire-safe redaction for complex secret-bearing Settings schemas. This plugin declares no secret Config fields and hides internal error text, but co-installed complex schemas still require an upstream fail-closed fix and re-validation.

License

MIT