m1khal3v/dsh-llm-key-rotation
Rotates to your next API key when a request hits a quota or 429, then retries, without restarting DSH or losing context.
LLM Key Rotation handles the case where an API key hits a quota limit or a 429 rate limit while you are working. Instead of surfacing the failure, the plugin swaps in the next key you have configured for that provider and retries the request immediately, so the agent and the user never see the failure and the conversation keeps its context. A cooldown discipline prevents the obvious failure mode: if every configured key is exhausted it stops rather than spinning through retries forever. Because it hooks the Harness recovery waterfall rather than patching core, installing and removing it are both clean operations.
Install
dsh plugin --profile web add @m1khal3v/dsh-llm-key-rotationThe npm line from the README. Keys are added and toggled from Settings in the web UI, and the README notes they are saved to the Harness credential store rather than to a plugin config file. The repository's own pnpm install line is for working on the plugin, not for using it.
Compatibility
Plugs into the Harness recovery waterfall with no core patches, which the README presents as making it safe to install and safe to remove. Rotation is per provider: the Settings page lists every key a provider can use and lets you toggle rotation on and off. Secret values are never logged, only provider names, indices and error codes.
Details
- Repo: m1khal3v/dsh-llm-key-rotation
- Category: Models & Providers
- Stars: 7
- Version: 1.1.0 (npm)
Alternatives
GooDAnDReaDY/dsh-key-rotation · zeng6125-rgb/dsh-llm-retry-settings · karoc/dsh-model-reasoning