omdsh-dev/omdsh-runtime
Adds deterministic plan/apply, candidate generations, explicit confirmation and previous-generation recovery on top of the official Harness Profile operations. Its portable format (omdsh-profile-pack/v1) records exact Registry project and Release IDs, author-owned sources pinned to full Git commits, the Registry snapshot, the observed @deepseek-ai/dsh version and one Agent Preset — deliberately not copying plugin payloads, credentials, sessions, environment files or absolute local paths. Applying a pack replaces only plugins governed by the pinned Registry snapshot plus fixed sources tracked by the same named pack instance, leaving other untracked local packages alone, and pack licenses reports each component's SPDX expression and provenance as an inventory (explicitly not legal advice).
Install
⚠️ Install command not yet confirmed — check the README on GitHub for the exact command.
Compatibility
A headless execution layer that reuses the official Harness Profile, Bundle, Cordis and package operations, so it does not introduce another Loader or a daemon. It expects an existing DSH runtime and profile; DSH Hub Workshop remains the only discovery, authoring, review and feed authority. Signed omdsh-profile-pack-envelope/v1 input is accepted for execution only when the publisher key is supplied and the Ed25519 signature verifies; unsigned v1 packs remain readable for compatibility.
Details
- Repo: omdsh-dev/omdsh-runtime
- Category: Other
- Stars: 2
- Version: @ohmydsh/runtime 0.1.0-preview.1 (npm preview dist-tag, registry-verified 2026-09-13; the README states preview releases never move latest implicitly)
- Last push: 2026-08-15
- First seen: 2026-08-13
Recent updates
The README documents the format versioning and compatibility rules (omdsh-profile-pack/v1 readable unsigned; envelope v1 accepted only with a verifying publisher signature) rather than release-by-release notes; preview releases stay on the preview dist-tag and never move latest. Verify the current package version and install steps before use.
FAQ
- Is omdsh-runtime a DSH plugin?
- No — it is a headless execution layer / CLI that reuses the official Harness Profile, Bundle and Cordis operations; the README states it does not create a second Loader, and plugins are still installed through the normal Harness flow.
- Does it replace the official plugin installer?
- The README says it reuses official Harness and package operations and only adds deterministic plan/apply, candidate generations, explicit confirmation and previous-generation recovery.
- Are unsigned packs still supported?
- Yes — unsigned omdsh-profile-pack/v1 packs remain readable for compatibility, while a signed omdsh-profile-pack-envelope/v1 is accepted for execution only when its publisher key is supplied and the Ed25519 signature verifies.
Alternatives
omdsh-dev/dsh-hub · omdsh-dev/fabric · omdsh-dev/plugin-template