Oh My DSH.DocsGitHub ↗
Documentation navigation

DOCUMENTATION Unpublished source candidate · 0.2.2-rc.5.omd.1.8.0

On This Page

Using OMD with other plugins#

中文 · Docs · Install · Plugin structure

OMD keeps DSH's native tools, skills, sessions and third-party plugin entries. Use plugins that match your full DSH version.

Versions must match#

OMD 1.8.0 is for DSH 0.2.2-rc.5, with OpenCU built in. Older DSH versions use their own older packages. IUI, OMAA and other separate projects also need the build for your DSH version.

Do not overwrite an install with an old package or by turning off version checks. Back up your data first and keep your settings, accounts and third-party sources.

Who owns the tools#

  • DSH manages tool registration, the SDK, scheduling, permissions, cancellation and plugin scopes.
  • OMD only provides PTC inside its own presets: business tools go through run_code, and the four background-job tools stay directly callable.
  • A tool visible in standard is not necessarily visible in every preset; check the actual scope.
  • Removing OMD only withdraws what OMD added. Wrappers, registrations and shared slots added later by third parties stay, and your original settings are not rewritten.

See prompt sources (Chinese).

OpenCU is built in#

With OMD installed there is no need to install OpenCU. You can also install OpenCU on its own; installed together, they share the same core and tools.

The embedded browser, annotations and native live view need a matching DSH desktop build; installing the plugin never changes stock DSH. Plain text and file work does not need computer use set up first. See computer and browser (Chinese).

Separate plugins#

Workflow, Rewind, DeepSeek Workbench, Persona, Extensions, OpenCU and theme management are all available separately, and Glyph ships with the theme plugin. Each separate version has its own DSH requirement. See plugin structure.

Plugin Relationship with OMD
Intelligent UI A separate interactive-content plugin. OMD provides the recommendation, version matching, shared slots and tool access, but not its implementation or data
OMAA Separate agent presets that work with OMD through workflow or mode entries
Subscription Login Separately handles sign-in, account pools, routing and Fast. OMD provides no accounts, quotas or priority
Intent assistant A separate plugin, off by default, unrelated to OMD's prompt enhancements and the ✨ optimizer
dsh-ops File, document and command tools by T-Auto, based on upstream 0.4.1; both normal mode and PTC keep DSH's permissions, sandbox and native tools
DeepSeek Workbench The built-in one is toggled under Features; a separately installed one is managed on the DSH Plugins page
OpenDesign and other standard plugins Keep their own skills, tools, interface, account requirements and licenses

Third-party catalog#

Settings → Oh My DSH → Third-party lists each plugin's purpose, original author, fixed source, supported DSH version, SHA-256 and status. Entries without a matching DSH version, a package or a release show no install button. Installs use the current profile's plugin manager; the desktop app uses itself or its bundled command line.

Current catalog: Billion Context 0.1.202, dsh-ops 0.1.0, Subscription Login 0.9.12, OpenDesign 0.1.0-omd.1.0.0, Intent assistant 0.3.4, Plugin Market 1.70.3, Infinite Gen 4 0.4.0, Status Rotator 0.38.0, DSH × Blender 2.6.1 and Balance Whale Widget 0.4.2. Set up accounts, Blender connections and paid requests as each plugin requires.

  • Older or incompatible installs show an Update button.
  • Automatic updates are off by default and only handle installed, enabled catalog entries. They never cross DSH versions, approve scripts or restart.
  • dsh-ops only installs registered compatibility builds, never upstream latest. If you install another version from a market or the command line, check it yourself.

Plugin install pre-check#

When you install, update or enable a plugin from the DSH Plugins page, a tool call or the desktop dsh-market, OMD first tries it in a temporary DSH. The plugin has to appear in the plugin list and load; blank pages, script errors and runtime errors are stopped. If it takes too long, it is marked "pre-check incomplete". It checks that the plugin starts properly, not that every feature works.

  • The pre-check uses the plugin code and enabled state you selected and copies no third-party private settings or accounts, so plugins that need external services may only show "incomplete". No API key is needed.
  • If first launch shows onboarding it continues through it; going straight to the main screen also counts as normal.
  • On macOS / Linux, the check stops if the processes use about 2 GiB of memory combined or temporary files reach about 1 GiB. Windows uses process-tree termination and timeouts.
  • It passes only after every check and process cleanup has finished. Early exits, crashes or cleanup timeouts never pass.
  • The pre-check installs no background service and leaves your command-line entries alone.
  • For updates from npm sources, it runs once before the whole update. Cancelling it never removes the old version first, and restoring the old version after a failed update is not checked again.

Plugins installed from the command line, npm / pnpm or by editing folders are not pre-checked.

Disabling and removing#

Disabling or removing OMD keeps conversations, drafts, attachments, settings, short memory and separate plugins' data. Old sessions created with an OMD preset may need OMD installed again to open.

When reporting a conflict, include the full versions of the plugins involved, load order, profile, the shortest steps to reproduce and the first error (with private data removed). Do not clear data or turn off every enhancement to hide a conflict. See troubleshooting and third-party notices.