Skip to content
dsh.fish
Bundle

dsh-plugin-oh-my-engine

An approval-gated OME engineering delivery agent preset for DeepSeek Harness

Source
oh-my-engine
stars
1 stars
License
MIT
Updated
Updated 5 days ago

Readme

# dsh-plugin-oh-my-engine

`dsh-plugin-oh-my-engine` adds the isolated `ome-engineer` preset to DeepSeek Harness Web and Desktop profiles. It keeps Oh My Engine platform-neutral: the plugin consumes OME's public lifecycle API and stores runtime state only in the active DSH Session Event Log.

![OME engineering mode lifecycle overview in DSH Desktop 2.0.4](assets/01-ome-engineering-mode-overview.jpg)

## DSH Desktop feature gallery

All screenshots below were captured from a real OME run in DSH Desktop 2.0.4. The run used an isolated demonstration workspace and completed the full Define → Plan → Build → Verify → Review → Ship → Learn lifecycle.

| Feature | Screenshot |
| --- | --- |
| Select the isolated **OME 工程化模式** Agent preset | ![OME Agent preset selector](assets/02-ome-agent-preset-selector.jpg) |
| Use the dedicated OME command palette | ![OME command palette](assets/03-ome-command-palette.jpg) |
| Stop at the Plan approval hard gate | ![OME Plan approval hard gate](assets/04-ome-plan-approval-gate.jpg) |
| Continue only after the user's `/ome-approve` command | ![OME user Plan approval](assets/05-ome-user-plan-approval.jpg) |
| Accept successful executed test output as verification evidence | ![OME executed test evidence](assets/06-ome-executed-test-evidence.jpg) |
| Complete Learn and record OME Memory | ![OME completion and Memory record](assets/07-ome-completion-memory.jpg) |
| Inspect the complete lifecycle in the DSH Session trace | ![OME Session trace](assets/08-ome-session-trace.jpg) |

## Install

Download the prebuilt package from the pinned GitHub Release. It includes the OME package built from the verified upstream commit, so neither package has to be published to npm and installation does not need Git or GitHub SSH:

```powershell
dsh plugin --profile web add https://github.com/oh-my-engine/dsh-plugin-oh-my-engine/releases/download/v0.1.6/dsh-plugin-oh-my-engine-0.1.6.tgz
dsh plugin --profile desktop add https://github.com/oh-my-engine/dsh-plugin-oh-my-engine/releases/download/v0.1.6/dsh-plugin-oh-my-engine-0.1.6.tgz
dsh plugin --profile desktop exec dsh-ome preset install
```

The plugin CLI is profile-local and is intentionally not added to the system `PATH`. Run it through the profile where the package is installed; replace `desktop` with `web` when installing only the Web profile.

Restart the profile host and select **OME 工程化模式**. The bundle patch only registers the OME Session Event Log vocabulary needed for cold-start resume; Standard, Code, Minimal, and other presets receive no OME tools, commands, or prompt changes.

### `EADDRINUSE` when starting DSH Web

The plugin installer does not start a web server. `EADDRINUSE 127.0.0.1:3080` means another DSH Web process already owns the default port; it is not an OME plugin installation failure. Diagnose it without platform-specific process commands:

```powershell
dsh plugin --profile web exec dsh-ome doctor
```

Reuse the already-running UI at `http://127.0.0.1:3080`, stop that process normally, or let DSH choose another free port:

```powershell
dsh web --port 0 --no-open
```

Preset lifecycle operations are explicit:

```powershell
dsh plugin --profile desktop exec dsh-ome preset update
dsh plugin --profile desktop exec dsh-ome preset remove
```

Update creates a complete backup. Update and remove refuse unmanaged or locally modified preset directories. Removing the plugin from a DSH Profile does not remove the preset, and removing the preset does not uninstall the Profile plugin.

## Role protocol

- `/ome-init` initializes OME without force or implicit overwrite.
- `/ome-approve` is the only accepted Plan approval source.
- `/ome-status` reads the current Session state.
- `/ome-cancel [reason]` cancels the current run.
- OME model tools manage lifecycle events only; DSH native tools retain ownership of edits, commands, sandboxing, approvals, and cancellation.
- Test evidence must reference a successful prior tool call in the same Session.
- Subagents inherit context but can only call `ome_status`.

First release support is Web and Desktop against DSH/Cordis `0.1.1-rc.2`. Re-run profile and Session compatibility checks before upgrading DSH.

See [OME Engineering Mode architecture, installation, acceptance, and rollback](docs/OME_ENGINEERING_MODE.md) for the complete delivery guide.

## Release information

- [Compatibility matrix](docs/COMPATIBILITY.md)
- [Publishing and DSH community submission](docs/PUBLISHING.md)
- [Changelog](CHANGELOG.md)
- [Security policy](SECURITY.md)

The canonical repository is `https://github.com/oh-my-engine/dsh-plugin-oh-my-engine`. The prepared community entry is stored under `community/` and is intentionally excluded from the npm package.

Install

dsh plugin --profile web add github:oh-my-engine/dsh-plugin-oh-my-engine

Profile: web

  • This package builds from source on install. pnpm will ask you to allow its build script — that is permission to run the package’s code on your machine, outside the agent sandbox. Only allow sources you trust.
  • This source has no pinned commit, so a later push upstream changes what installs. Prefer pinning a commit.
Source