AI Agent Hub
Back to plugins
🖥️

dsh-llm-retry-settings

Client Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install Yiklek/dsh-llm-retry-settings

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

Run dsh plugin install Yiklek/dsh-llm-retry-settings in the DeepSeek Harness terminal; the source code is hosted at https://github.com/Yiklek/dsh-llm-retry-settings , and once installed you can manage per-provider retry and timeout policies from the settings page.

About this plugin

Tweaking a specific LLM provider's retry mode, max retries, or timeout values in DSH used to mean digging into per-provider YAML namespaces and double-checking syntax by hand. dsh-llm-retry-settings moves that work into a clean settings page: retry policy (normal or always mode, maxRetries) alongside timeoutMs, websocketConnectTimeoutMs, and streamIdleTimeoutMs, all grouped by provider and editable in place.

Every save goes through the settings.mutate wire face, so the change is picked up by the very next model request without restarting the gateway or reloading your profile. Timeout fields are auto-discovered from each provider's settings schema when available, with a verified fallback map for the bundled providers such as llm-pi-ai and llm-deepseek, so new providers often light up automatically.

This plugin is a good fit for DSH users who run multiple LLM providers and want per-provider retry and timeout tuning without repeatedly hand-editing config files. It ships as a pure client-side bundle with an empty host half, hooks into your profile bundles on install, and requires no manual patch edits to cordis.patch.yml.

Use Cases

  • Tune retry mode and max retries per LLM provider without touching raw YAML files.
  • Adjust stream idle timeout values to improve stability of long-running generation requests.
  • Switch between normal and always retry policies in the GUI; changes apply on the next model request.

Best For

  • DSH users running multiple LLM providers who need per-provider retry and timeout tuning.
  • Developers who prefer a visual settings page over hand-editing config files to reduce errors.
  • DSH users focused on gateway retry and timeout behavior to keep generation requests stable.