Configuring model capabilities in DeepSeek Harness (DSH) usually requires manually editing the settings.yaml file, which is cumbersome and error-prone. The DSH plugin dsh-awesome-model-setting adds a “Model Capabilities” page to the settings panel, allowing users to declare a model’s input modalities, context window, maximum output tokens, and image quota directly through a graphical interface without touching configuration files.

Core Features

  • Adds a “Model Capabilities” page to the settings panel.
  • Graphically edit model capabilities (input modalities, context window, maximum output tokens, image budget).
  • Shows merged effective values (your settings document merged with the adapter catalog).
  • Supports loading model lists from providers.
  • Supports resetting to default parameters.
  • Supports restoring route defaults.

Install and Enable

  1. Use the official install command to add the plugin:
dsh plugin --profile web add github:Kazusa1085/dsh-awesome-model-setting

  1. Restart the DSH Web service.

  2. Open Settings and go to the “Model Capabilities” page.

Typical Usage

  • Fetch model list: On the page, each registered route group has a “Load from provider” button. After clicking it, the plugin asks the adapter which models that route can provide. For routes with an adapter-provided catalog, the list is local; for manually declared routes (such as local servers), the plugin requests the baseURL/models endpoint (with a maximum wait time of 15 seconds) to obtain the model inventory. The list marks model status as “declared,” “added,” or “provided by catalog.”
  • Edit capability parameters: Modify input modalities, context window, maximum output tokens, or image budget directly in the graphical interface. After saving, the effective values are the merged result of your configuration and the adapter catalog.
  • Use defaults: If a numeric input field (context window, maximum output, image budget) is left blank, it means the field is removed from the document and the default value is used instead. In this case, the input box displays the placeholder text “Use route default,” but the effective value is still shown in the label (for example, inherit <value>).
  • Restore route defaults: This button appears only if the input modalities you declared are actually different from the adapter defaults. Clicking it restores the model’s capability fields (modalities, context, output, image budget) to the route’s default declaration. The change is pending and must be saved to be written.
  • Reset to default parameters: This button appears only on routes with an adapter-provided catalog. Clicking it resets the parameters of all models under that route to default values. It does not modify the model list or display names.

Applicable Scenarios and Notes

  • This plugin is suitable for scenarios requiring fine-grained management of multimodal model configuration, especially when adapter-provided catalogs (such as llm-pi-ai) coexist with manually declared routes.
  • The displayed values are “effective values,” meaning the result of merging your configuration with the adapter catalog.
  • The “Restore route defaults” button appears only if the input modalities you declared are actually different from the adapter defaults.
  • “Reset to default parameters” appears only on routes with an adapter-provided catalog and is not shown for manually added providers (local services), because there are no built-in defaults to fall back to.
  • When modifying a model whose capabilities come from a catalog declaration (marked with a “route declaration” label), a confirmation dialog appears first to ask whether you want to override them.
  • The plugin runs with the permissions of the current DSH process. Please make sure you understand the source code and license (MIT).

This plugin simplifies the model capability configuration process through a graphical interface, transforming configuration changes from file editing into intuitive operations.