AI Agent Hub
Back to plugins
🖥️

dsh-retry-policy-settings

Client Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install guanosine-diphosphate/dsh-retry-policy-settings

Paste the following prompt into your AI chat to install this plugin:

Install from https://github.com/guanosine-diphosphate/dsh-retry-policy-settings by running dsh plugin install guanosine-diphosphate/dsh-retry-policy-settings, then add dsh-retry-policy-settings to dsh.profile.bundles in your profile and restart the Web UI.

About this plugin

When running multiple LLM providers under DeepSeek Harness, the API retry policy is buried deep in settings.yaml — mode, maxRetries, retryableCodes, and the three backoff parameters carry cross-field constraints that make manual YAML editing tedious and error-prone. dsh-retry-policy-settings lifts every field into the DSH Web settings panel so you can configure retries visually and have changes take effect immediately via hot-reload.

Navigate to Settings → Model Retry Policy. The plugin auto-discovers every registered provider in your profile (custom OpenAI-compatible endpoints, DeepSeek official, etc.) and renders its full retryPolicy as a form. In normal mode you tune max retries, pick retryable error codes, and set the exponential-backoff initial delay, max delay, and jitter ratio; switch to always mode and schema-forbidden fields disable themselves, staying strictly aligned with the official @deepseek-ai/dsh-llm-retry RetryPolicySchema. Save and the change hot-reloads with no restart required. A one-click reset restores the default policy at any time. The UI follows the global DSH locale and adapts to dark or light themes automatically.

Ideal for developers and operators running a DSH Web profile with one or more LLM providers who want fine-grained control over failure-retry behaviour. If you have been editing YAML by hand to tweak retry parameters, this plugin makes the task as simple as filling in a form.

Use Cases

  • Tune retry counts and exponential-backoff parameters across multiple LLM providers
  • Switch a provider to always-retry mode to handle unstable network connections
  • One-click reset to restore the default retry policy

Best For

  • Developers running DSH Web profiles with multiple LLM providers
  • Operators who need fine-grained control over API failure-retry behaviour
  • Technical users who prefer visual configuration over manual YAML editing for retry parameters