Introduction

The philosophy of DSH is “everything is a plugin”. If you want the main agent to focus only on planning and dispatching, delegating specific tasks to specialist subagents, while also being able to switch different model combinations, dsh-plugin-omoslim is a ready-to-install DSH bundle.

It installs an orchestrator agent preset, separating model selection, persona combinations, and plugin updates. The main agent handles plan and dispatch, while model-pinned specialist subagents handle the specific work.

What is this

dsh-plugin-omoslim is an MIT-licensed DSH bundle, repository address is:

https://github.com/tevenfeng/dsh-plugin-omoslim

It installs an agent preset named orchestrator and provides 11 subagent tools. According to verified descriptions, these specialist subagents include roles such as explorer, oracle, librarian, designer, fixer, and council.

The DSH plugin ecosystem is a community plugin/directory ecosystem, not the official app store of DeepSeek or Huaxuan.

Core Capabilities

Installing an Orchestrator preset

After installation, you can use the orchestrator preset. The main agent is responsible for planning and dispatching, while subagent tools handle specific tasks.

The value of this preset lies in separating “who plans” from “who executes”, rather than having one agent handle all steps simultaneously.

Separating model definitions and persona combinations

The plugin places the model/provider in independent profiles, located at:

~/.dsh/.agent-presets/orchestrator/models.d/

The goal of this is: when updating the plugin, it should not directly overwrite user-adjusted model selections.

If a subagent’s provider is null, it means it inherits the main agent’s provider.

Managing multiple model profiles

You can maintain multiple named profiles under the same preset and query/switch them via the omoslim CLI.

Verified commands include:

omoslim list
omoslim current
omoslim switch economy

Where omoslim switch economy means switching to a profile named economy.

Viewing current subagent models in the Web UI

The plugin provides a web UI subagent model inspector to view the provider/model of each subagent under the active profile.

This inspector targets the active orchestrator session. Its read-only interface is:

GET /dsh-plugin-omoslim/subagent-models

Installation and Activation

The following is a verified installation method. The installation command assumes the use of the web profile directory, where web is the default profile.

dsh plugin --profile web add dsh-plugin-omoslim

After installation, restart the web service or dsh web process:

systemctl --user restart dsh-web

If your dsh web was started by other means, you can also restart that process directly.

For local development scenarios, you can first install using a local directory:

pnpm add file:/home/<you>/Coding/dsh-plugin-omoslim

Then add the package name dsh-plugin-omoslim to the dsh.profile.bundles array.

Typical Usage

  1. Install the plugin:
dsh plugin --profile web add dsh-plugin-omoslim
  1. Restart:
systemctl --user restart dsh-web

  1. Open the web UI, start a new session, and select the orchestrator preset in Settings → General.

  2. View the current profile:

omoslim current
  1. List available profiles:
omoslim list
  1. Switch profile:
omoslim switch economy
  1. If you need to modify the model or provider for a specific slot, edit the corresponding profile file:
~/.dsh/.agent-presets/orchestrator/models.d/<name>.json

After modifying, switch to that profile, then restart dsh or dsh-web, and create a new session.

Uninstallation and Rollback

Uninstall the bundle:

dsh plugin --profile web remove dsh-plugin-omoslim

Preset files may still remain in:

~/.dsh/.agent-presets/orchestrator/

If you confirm you are no longer using this preset, you can delete that directory. If you just want to remove the plugin but continue using the installed preset, you can also keep this directory.

Notes

  • A profile must name every slot referenced by the template. If a slot is missing, the plugin will fail closed, rather than rendering a half-filled composition.
  • If you manually edit agent.cordis.yml, the plugin will preserve your file after detecting a hash difference. In this case, you are responsible for this file; if you wish to accept plugin updates, you need to delete the preset directory.
  • After switching the active profile, you need to restart dsh or dsh-web and create a new session for the new models to load.
  • After updating the plugin, you need to restart the web app for new routes and buttons to take effect.
  • Model and provider names in the documentation may come from an example environment and must exist in your chosen provider catalog in actual use.
  • The plugin will run with the permissions of the current dsh process. It is recommended to check the source code and MIT license before installation.

GitHub:

https://github.com/tevenfeng/dsh-plugin-omoslim

Directory page: No specific URL was provided in verified materials. If you use the DSH community directory, you can search for the plugin name dsh-plugin-omoslim.