Provides automatic LLM model fallback chain for DSH agents: automatically switches to the next backup model when requests trigger authentication, quota, or rate limit errors, ensuring uninterrupted task execution.
- Language
- TypeScript
- License
- MIT
- Branch
- main
Install
$ dsh plugin --profile web add github:btspoony/dsh-llm-fallbacksRun the command above in your terminal to install this plugin via the dsh CLI. You can switch Profile in the top-right corner. New to dsh? Read the beginner tutorial
Install via your agent
Install the DeepSeek Harness plugin btspoony/dsh-llm-fallbacks for me: review the repository at https://github.com/btspoony/dsh-llm-fallbacks first, then run the install command and verify the plugin loads successfully.
Paste this instruction to the DSH Web GUI assistant — it will install and verify for you.
One-line Summary
Adds automatic fallback chains for LLM requests in DSH (DeepSeek Harness) agents: when authentication fails, quota runs out, or rate limiting (429) occurs, the plugin automatically switches to the next available provider/model along a pre-configured sequence, allowing the current step to continue without interruption.
Core Capabilities
- When requests from main or sub-agents fail, automatically falls back to the next provider/model in the chain, keeping the task uninterrupted
- The new "FallbacksChain / Auto" virtual entry in the model selector allows using the entire chain as the primary choice, rather than only intervening on failure
- Provides 7 built-in sub-agent roles (
task/sonic/scout/designer/librarian/reviewer/security-reviewer) that can be directly referenced by rules - Supports switching effective root chains by time period (peak/valley windows): 4固化 UTC+8 presets + custom windows, the first matching row's chain replaces the all-day chain
- During dispatch, intelligently locks sub-agent roles through three-stage parsing (explicit → rule → LLM auto-match), and injects the first specific model from that role chain into the initial request
- Two safety valves: max switch count per step and always-mode retry cap, preventing chain loops from amplifying latency
Technical Implementation
- Language: TypeScript (host-side + client-side React components), outputting ESM
- Key Dependencies:
@deepseek-ai/cordis^4.0.1 (host service injection),@deepseek-ai/dsh-settings(settings namespace registration),@deepseek-ai/dsh-typert-protocol+dsh-typert-registry(self-built/api/fallbacks/*gateway channel),@deepseek-ai/schemastery^3.18.1 (settings schema) - Architecture Pattern: mount-only cordis plugin——
bundle/cordis.patch.ymlonly inserts one lineid: llm-fallbacks, the host side intercepts requests through two cordis hooksagent/request-errorandagent/request, the client side registers a settings card throughsettings.plugin.itemslot + registers a virtual provider throughllm.registerAdapter; the built-in typert gateway (/api/fallbacks/get|set|reset|revert-seed) is the only write path, does not modify dsh source code - Entry Files:
src/index.ts(host-sideapply()),src/client/index.ts(client-sideapply()), respectively loaded by bundle patch anddsh.client.injectlist
Applicable Scenarios
When DSH users use multiple models like DeepSeek / Anthropic / OpenAI, a single provider experiencing 429, quota exhaustion, or authentication failure can stall the entire task. After installing this plugin, configuring a chain like "preferred Anthropic, fallback DeepSeek V4 Flash, final fallback DeepSeek V4 Pro" ensures single-point failures no longer block tasks. Multi-model users, users with self-built/third-party multi-provider configurations, and users who want to switch different model pools for peak/valley periods are the best fit.
Prerequisites and Compatibility
| Dependency | Minimum Version | Description |
|---|---|---|
| DSH | ^0.1.1-rc.1 | All @deepseek-ai/dsh-* peer dependencies are ^0.1.1-rc.1; dsh-tui settings panel requires ≥ v0.8.5 (README.md:145) |
| Node.js | >=22 | package.json:56-58 declares engines.node: ">=22"; build uses pnpm ≥ 10 / project stack pnpm 11.21+ |
| Platform | Cross-platform | package.json doesn't declare os / cpu, no native module dependencies |
| Native Modules | None | No native bindings like node-pty, node:sqlite introduced |
Installation
dsh plugin --profile web add github:btspoony/dsh-llm-fallbacks
Configuration Options
All plugin configurations fall under the dsh settings document's fallbacks: namespace and can be edited in Settings → Plugins → Fallbacks card, $DSH_HOME/settings.yaml file, or dsh-tui's /settings area. Description column is in plain language, full field constraints see docs/configuration.md.
| Config | Type | Description | Default |
|---|---|---|---|
enabled | boolean | Master switch; when closed the plugin is completely no-op | false |
triggerCodes | string array | Failure codes that trigger fallback decision (5xx is retried first by llm-retry) | ['AUTH', 'QUOTA', 'RATE_LIMIT'] |
rootChain | string array | All-day fallback chain: preceding items are fallback chain, the last item must be an official V4 model (Flash or Pro) as final fallback | [] |
cooldownMs | number | How many milliseconds a switched-out/failed model won't be selected again | 300000 (5 minutes) |
revertPolicy | enum | Whether to automatically return to main model after cooldown expires | cooldown-expiry |
maxSwitchesPerStep | number | Max switches per step; exceeding stops switching | 8 |
alwaysModeRetryCap | number | Switch after how many always mode retries; 0 disables | 5 |
presets | enum | Whether to auto-declare 7 built-in sub-agent roles on apply | bundled |
roleAutoMatch | boolean | Whether to allow LLM auto-matching roles on sub-agent's first request | true |
timeSlots | array | Time slot rows (4固化 presets + custom windows); first matching row's chain replaces all-day chain | [] |
tz | string | Timezone for time slot matching (standard Intl rules, DST-safe) | Asia/Shanghai |
roles.list | array | Custom sub-agent role list, each must have at least one chain entry | [] |
roles.rules | array | Rules mapping sub-agents to roles (match by provider/model pattern) | [] |
FAQ
Q: Will this plugin immediately change my model behavior after installation?
A: No. enabled defaults to false, and the config is no-op with no chains configured, just like not having it installed. You need to open the switch in the Fallbacks card and fill in rootChain, then restart the session for it to take effect.
Q: Will 5xx temporary errors be managed by the fallback chain?
A: 5xx is first retried with backoff by the host's llm-retry plugin; only after its budget is exhausted does this plugin's decision path run; no need to add 5xx to triggerCodes (docs/configuration.md:25).
Q: How should I set it up if I want the primary choice to directly use the "head" of the fallback chain?
A: Just select the FallbacksChain / Auto virtual entry in the web or dsh-tui model selector—it will use the first specific model of the current day's effective chain as the primary; selecting any real model preserves fallback-only behavior.
Q: After upgrading to 0.2.2+, historical sessions won't open. What should I do?
A: Versions before 0.2.2 wrote fallbacks/switch durable events to sessions, which new dsh refuses to load. First stop dsh, clone this repo, then run pnpm repair:fallbacks-switch-logs -- --apply --backup. The script will mark old events as ignorable to restore session loading.
Q: If I edit settings.yaml directly, will it take effect in real-time?
A: YAML is the shared source of truth; web card and TUI both read from here. You need to restart the current dsh session for config changes to be picked up by the plugin (README.md:70-74).
Q: What if there's no settings panel in my terminal profile?
A: Requires dsh-tui ≥ v0.8.5. Older dsh-tui versions won't see the Fallbacks editing area in /settings, only file editing; functionality still runs, just no GUI.
Q: Any extra operations needed when uninstalling?
A: Just run dsh plugin --profile web remove dsh-llm-fallbacks and restart the session. This plugin has no postinstall hooks and didn't modify dsh source code.
Learning Curve
Beginner — The plugin is completely no-op under default configuration; at minimum, just open enabled in the settings card and fill in one line of rootChain to get the fallback engine running. Complex time slot switching and role rules can be added as needed.
Known Issues and Limitations
- Does not automatically rewrite old (two-era)
chains/roles.defaultconfig; only prints warning at startup and shows migration banner at panel top, requires manual migration perdocs/configuration.mdmigration table (src/index.ts:436-439,README.md:133). - Versions before 0.2.2 wrote durable
fallbacks/switchsession events, issue #52 (event type registration fails under different module instances on apply()) confirmed; from 0.2.2+ the plugin stops writing new events, but old sessions need thescripts/repair-fallbacks-switch-logs.tsscript in the repo to mark as ignorable to reload (src/index.ts:672-678,README.md:46-58). - Time slot presets (
liang-peak/liang-valley/glm-peak/glm-valley) windows are固化 UTC+8 code constants, preset rows in config cannot carrystart/end/days/namefields; rejected by gateway on save, warned and skipped on load if present (src/time-slots.ts:106-152,src/config.ts:236-241). - When
rootChaindoesn't end with an official V4 model (Flash or Pro), there's a warning at startup; time slot rows are invalid at this time, andFallbacksChain / Autoin model selector also refuses to override (src/config.ts:236-241,src/virtual-adapter.ts:287-298). agent/request-errorhook must be ordered after hostllm-retry; the plugin's bundle line is auto-appended to stack end viadsh plugin add, satisfying order; when manually modifyingdsh.profile.bundlesneed to ensure@deepseek-ai/dsh-baseis before this plugin (docs/install.md:31-37).
Automatic provider/model fallback chains for dsh (DeepSeek Harness): when an agent's LLM requests keep failing — retries exhausted, auth errors, quota exceeded, rate limiting (429) — the plugin switches provider/model along the fallback chain for the current role, and the current step/turn continues on the target model: tasks are not interrupted by model problems.
Works in both dsh front ends: the web profile (Settings → Plugins → Fallbacks card) and the dsh-tui terminal profile (/fallbacks session diagnostics, /fallbacks config readback, and the /settings fallbacks section for editing).
Time slots
Time slots rotate the effective root chain by wall-clock windows: each slot row carries its own fallback chain, and the first row whose window contains the current moment replaces the all-day chain for the next root request — the all-day chain stays as the last resort when no slot matches. Peak and valley windows can therefore use different chains while the failure walk (fallback switch) remains untouched.

Four frozen UTC+8 presets (windows are code constants; preset rows lock tz to Asia/Shanghai):
| Preset | Window |
|---|---|
liang-peak | 09:00–12:00 and 14:00–18:00, every day |
liang-valley | every other UTC+8 time (complement of Liang Peak) |
glm-peak | Monday–Friday 14:00–18:00 |
glm-valley | every other time (complement of GLM Peak) |
GLM Peak and GLM Valley are offered in the card picker only when zai-coding-cn is configured.
The first extra row whose window contains the current moment (in fallbacks.tz, default Asia/Shanghai) wins; no match → the all-day rootChain, whose tail (Default model) must be exactly one official V4 model — deepseek-official/deepseek-v4-flash XOR deepseek-official/deepseek-v4-pro. Slot rotation is a routing seed, not a failure decision: it applies on the next root request, consumes no cooldown, and is logged as a time-slot switch — failure walks keep fallback switch. Full semantics → Time-slot presets and docs/configuration.md.
Quick start
Install
dsh plugin --profile web add dsh-llm-fallbacks # web profile (Settings → Fallbacks card)
dsh plugin --profile dsh-tui add dsh-llm-fallbacks # dsh-tui terminal profile
Same plugin, either front end — the only difference is the --profile flag. Pin a version with @<version>. A registry install fetches the built package (dist/), nothing builds on the target machine. Registry / git / local-directory variants, uninstall, and --dump-config verification → docs/install.md.
Repair existing sessions (versions before 0.2.2)
Versions before 0.2.2 wrote durable fallbacks/switch session events that newer dsh releases refuse to load (issue #52 — the apply()-time event-type registration is ineffective because plugin and host resolve different module instances). If existing sessions fail to open after an upgrade, clone this repository and repair the logs (stop dsh first):
git clone https://github.com/omdsh-dev/dsh-llm-fallbacks.git
cd dsh-llm-fallbacks
pnpm install
pnpm repair:fallbacks-switch-logs -- --dry-run # preview which sessions would change
pnpm repair:fallbacks-switch-logs -- --apply --backup # mark legacy events ignorable
The script scans ~/.dsh/sessions by default (override with --root <dir>), marks legacy fallbacks/switch events ignorable: true so the host read path accepts the session again, and keeps a <file>.bak per repaired log. --apply requires --backup and must run with dsh stopped. From 0.2.2 on, the plugin stops writing durable switch events, so no new sessions need repair.
Configuration surfaces
The plugin's settings live in a shared fallbacks: namespace, editable from three surfaces:
| Surface | What it is | Notes |
|---|---|---|
| Web settings card | Settings → Plugins → Fallbacks | Full GUI editor for the fallbacks: namespace; writes the shared settings document |
$DSH_HOME/settings.yaml | fallbacks: section in the dsh settings document | The shared source of truth — the same file the web card writes; readable and editable everywhere, including scripted setups |
TUI /settings | fallbacks section in the dsh-tui settings screen | dsh-tui ≥ v0.8.5; native fields for simple keys, JSON text fields for complex structures (see dsh-tui profile (terminal)) |
Pick the surface that matches your front end: web users get the card, terminal users get /settings, and the YAML file works everywhere. (/fallbacks and /fallbacks config are diagnostics — read-only views, not edit surfaces.)
Minimal configuration
Add a fallbacks: section to the shared settings document ($DSH_HOME/settings.yaml — see Configuration surfaces):
fallbacks:
enabled: true # feature switch — defaults to off (plugin is a no-op otherwise)
rootChain: # all-day chain: leading entries = fallback walk, last = Default model (official V4)
- anthropic/claude-3-5-sonnet # walked first
- deepseek-official/deepseek-v4-flash # last resort (Flash or Pro)
timeSlots: # optional: rotate the effective root chain by wall-clock windows
- kind: preset # frozen UTC+8 window; only the chain is editable
preset: liang-peak # 09:00–12:00 and 14:00–18:00, every day
chain:
- anthropic/claude-3-5-sonnet
- kind: custom # custom window (may wrap midnight)
name: evening # optional display name
start: '22:00'
end: '02:00'
days: [1, 5] # optional; omitted/empty = every day (0=Sunday…6=Saturday)
chain:
- openai/gpt-4o
roles: # optional: declare role entities, then reference them from rules
list:
- id: reviewer # unique id; "inherit" is reserved
persona: Code-review subagents
chain:
- openai/gpt-4o-mini
fallback: inherit-root # role chain first, then the inherited rootChain
rules: # subagent-only: rules never match root requests
- role: reviewer # all subagents → the reviewer role
Build the section up in four steps:
1. Enable the plugin. enabled: true turns the fallback engine on. It defaults to off — with no chains configured the plugin is a complete no-op.
2. Set the all-day rootChain. Leading entries are the fallback chain, walked first when a request fails; the last entry is the Default model.
Conformance: the last entry must be exactly one official V4 model —
deepseek-official/deepseek-v4-flashXORdeepseek-official/deepseek-v4-pro. The settings card and gateway reject any other tail on save; a legacy non-official tail warns at startup and keeps working as a fallback-only walk, but cannot be saved as-is.
3. Add timeSlots (optional). Rows rotate the effective root chain by wall-clock windows. Preset rows use frozen UTC+8 windows (only their chain is editable; while a preset row exists, tz locks to Asia/Shanghai); custom rows take start/end (may wrap midnight) and an optional days list. The first row whose window contains the current moment wins; no match → the all-day rootChain. Rotation is a routing seed — it applies on the next root request and consumes no cooldown (see Time slots).
4. Add roles (optional). Declare role entities in roles.list (id, persona, chain, optional fallback policy), then map subagents to them with roles.rules. Rules never match root requests — with no rule match (or on a root request) the built-in inherit role applies and appends the rootChain.
Full reference (role entities, fallback strategies, rules, selectors, preset roles, time-slot presets) → docs/configuration.md.
Upgrade note (behavior change): an existing
fallbacks:section without an explicitenabledkey resolves tofalseafter upgrading — addenabled: trueto keep the plugin active.
Verify
Save the config and restart the session, then type /fallbacks — the read-only in-session diagnostics (origin, resolved role, chain, recent fallback switches, cooldown status). In a dsh-tui profile, /fallbacks config reads back the composed configuration; see dsh-tui profile (terminal).
Features
- Automatic fallback for root and subagents: any agent switches down the chain to the next available provider/model on model failure — no manual model switching.
- Two-block config:
rootChainfor the root agent; declared role entities (roles.list) referenced byroles.rules(or the built-ininherit). - Chain as root primary from the picker: when
enabledis on, the host model picker (web and TUI alike) shows a virtualFallbacksChain/Autorow — selecting it uses the configured chain as the root primary (a conforming all-day head is required for the override to succeed); selecting a real model keeps fallback-only (see FallbacksChain in the model picker). - Time slots: optional
fallbacks.timeSlotsrows rotate the effective root chain by wall-clock windows in the config-leveltztimezone (defaultAsia/Shanghai) — four frozen UTC+8 presets (liang-peak/liang-valley/glm-peak/glm-valley, windows are code constants, models-only edits) or customstart/end/dayswindows. The first matching row wins; the all-day row is always last. A slot change applies on the next root request and is logged as a time-slot switch — a routing seed, never a failure decision: it consumes no cooldown and does not count againstmaxSwitchesPerStep. Failure walks keep the fallback switch copy (see Time-slot presets). - Dispatch-time role resolution: on a subagent's first request its role is resolved in three stages — explicit (
agentPresetmatches a declared role id) → deterministic rules (unchanged) → LLM auto-match from the declared role taxonomy (fallbacks.roleAutoMatch, defaulttrue). The resolved role's chain-head model is injected into the first request and recorded via an explicitrole → modellog line (no durablefallbacks/switchevent is written — issue #52 stop-write); setroleAutoMatch: falseto disable the LLM auto-match stage (the explicitagentPresetstage still applies — with no explicit role this reproduces the previous rules-only behavior). The settings card always renders an Enable role auto-match switch (defaulttrue) to toggle it — the schema default applies even to legacy configs that never declared the key. - Cooldown and revert: failed / switched-away models are not re-selected during cooldown;
revertPolicy: cooldown-expiryreturns to the primary model automatically. - Visible behavior: every switch is recorded in an info-level log line (from/to/role/reason) — no silent model switching. The plugin deliberately writes no durable
fallbacks/switchsession events (issue #52: the apply()-time event-type registration was proven ineffective, and a session containing the event refused to load after a dsh restart). Sessions written by older plugin versions that contain such events are repaired byscripts/repair-fallbacks-switch-logs.ts, which marks legacy events ignorable so affected sessions load again. - Safety valves:
maxSwitchesPerStepcaps switches per step andalwaysModeRetryCapcaps always-mode retries — chain loops cannot amplify latency. - No-config no-op: with no chains configured the plugin behaves exactly like not being installed (
enabledis off by default — see Minimal configuration).
dsh-tui profile (terminal)
In a dsh-tui profile the plugin has three operator surfaces, with a strict duty split:
/fallbacks— what happened this session: origin, resolved role, effective chain, recent fallback switches, cooldown status. Read-only./fallbacks config— what is configured: composed-config readback (trigger codes, root chain, time slots, timezone, roles, role rules, cooldown, revert policy, safety valves, presets, role auto-match). Read-only apart from the one action command/fallbacks config revert-seed <role-id>, which restores a seeded role's persona to its declared seed default (a web-card action the settings seam cannot express)./settings— the edit surface. The plugin registers a fallbacks section with full parity to the web settings card: booleans (enabled,roleAutoMatch) render as toggles, selects (presets,revertPolicy) as pickers, and numbers (cooldownMs,maxSwitchesPerStep,alwaysModeRetryCap) as numeric inputs; complex structures (rootChain,timeSlots,roles.list,roles.rules) are JSON text fields andtriggerCodesa comma-separated text field. Invalid drafts (bad JSON, non-conforming chains, malformed time-slot rows) block the save — the section never corrupts the config.
Requirements: the /settings fallbacks section needs dsh-tui ≥ v0.8.5 (commit c51661f or later on main; the settings seam shipped in v0.8.0, the groups shape + validation in v0.8.5). On an older dsh-tui the section is absent, and file editing remains the only TUI edit surface.
File editing still works everywhere: the shared $DSH_HOME/settings.yaml (fallbacks: section — the same file the web card writes) for global settings, or the profile patch ~/.dsh/profiles/dsh-tui/cordis.patch.yml (config: overrides on the plugin row) for dsh-tui-specific values. A patch row replaces the targeted row's whole config — restate every field you want to keep (schema defaults fill the rest).
FallbacksChain in the model picker
When enabled: true, the plugin registers a virtual provider, FallbacksChain, with a single catalog row: Auto. The web profile and dsh-tui both see the row: they share the same adapter catalog, so the row needs no settings-page wiring or host patch (it is independent of the /settings fallbacks section, which edits configuration rather than the picker catalog). The row is visible whenever the plugin is enabled — a legacy or empty all-day chain does NOT hide it (the override just refuses to fire).
Selecting FallbacksChain / Auto uses the configured chain as the root primary: root requests route to the effective chain's first exact provider/model at request time, and the fallback engine degrades from that head as usual. Selecting any real catalog model keeps the v0.2.2 fallback-only behavior — the session model is primary and the chain engages only after it fails.
There is no rootMode switch — no config key, YAML field, settings toggle, or gateway flag. The mode is the session's {provider, model} selection itself: FallbacksChain = chain primary; any real model = fallback-only.
Notes:
- Picker label: the row's catalog
name(what the composer trigger shows) is live —Auto: DeepSeek V4 Flash[Liang Peak]/Auto: DeepSeek V4 Flash[all-day](catalog display name, not the model id); the id staysAuto. BareAutoif the all-day tail is not conforming. Refresh by reopening the picker. - Root only: the row is about the root agent. Subagent role resolution and injection are unchanged; a subagent session that inherits the selection still routes through the chain head — the virtual row is a thin delegate, never a second routing engine.
- Conformance gate on the tail: a successful override/delegate requires the all-day chain to be tail-conforming — its last entry must be exactly one official V4 model (
deepseek-official/deepseek-v4-flashordeepseek-official/deepseek-v4-pro, the card's Default model panel); leading entries (Default fallback chain) are walked first. Disabling the plugin hides the row again (slot-row/chain edits never churn registration). - Stale selection: if the row disappears (plugin disabled) while
FallbacksChain / Autois selected, the session keeps showing it as the current model withroutable: false— pick a real model from the catalog to continue (host-native catalog semantics). - Capabilities follow the head: the row's model metadata (context window, modalities, reasoning) mirrors the current effective head; retry attribution follows the permissive default — retries/failures are accounted to the real head pair, not to the
FallbacksChainprovider. Full semantics → docs/configuration.md.
Time-slot presets
Time slots are introduced in the featured overview above; this section is the reference. Time-slot rows rotate the effective root chain by wall-clock windows — useful for peak/valley pricing without confusing wall-clock rotation with failure fallback. The copy split is strict: slot rotation logs and UI say time-slot switch; the failure walk keeps fallback switch; the conversation notice Model downgraded stays on the failure path only.
- Match order: at every root request, the first extra row whose window contains the current moment (in
fallbacks.tz, defaultAsia/Shanghai/ UTC+8) wins — that row's chain replaces the all-day chain. No row matches → the all-dayrootChainis used. The all-day row is always last and required: its last entry must be exactly one official V4 model (Flash XOR Pro; leading Default fallback chain entries are walked first). - Presets (frozen, not user-editable):
liang-peak= 09:00–12:00 and 14:00–18:00 every day;liang-valley= every other UTC+8 time;glm-peak= Monday–Friday 14:00–18:00;glm-valley= every other time. One preset id = one row; the card picker never offers a duplicate. - Custom rows:
start/end(HH:mm, may wrap midnight) + optionaldays(0=Sunday…6=Saturday; omitted/empty = every day) + models. - Next-request apply: a slot boundary crossing never preempts an in-flight step — the new row takes effect on the next root request. Rotation is mount-only: info log + card/
/fallbacksstatus line, no durable switch event. - Settings card: the Main agent section groups Time slots (extra rows — add preset / add custom / remove / reorder by buttons or drag; preset rows show a read-only window summary and edit models only; custom rows carry an editable name; the timezone picker lives here and locks to Asia/Shanghai while any preset row exists, since preset windows are frozen UTC+8 constants), Default fallback chain (walked first when no slot matches) and Default model (the official V4 Flash | Pro last-resort fallback). Rows are collapsible to name + first model. There is no
timeSlots.enabledmaster switch (adding a row is the opt-in) and norootModecontrol.
Preset roles
The plugin ships 7 bundled generic subagent roles out of the box — designer / librarian / reviewer / scout / security-reviewer / sonic / task — declared automatically on apply as seeded roles.list rows ({ id, persona }): idempotent, and never overwriting an operator persona. They appear in the Settings card (seed badge, id immutable) and in the /fallbacks config role summary, ready for roles.rules to reference.
- Switch:
fallbacks.presets—'bundled'(default) declares the preset roles on apply;'none'disables the automatic declaration (already-materialized rows stay). - Full semantics (upgrade behavior, conflict handling, library reuse of
presetRoles) → docs/configuration.md.
Mount-only (no dsh modification)
The plugin installs as a pure mount: bundle insert + client inject + its own gateway channel (/api/fallbacks/get|set|reset) — no dsh patches, no postinstall step, and dsh upgrades never require re-patching. Stale leftover patches from an older patched install are harmless.
Documentation
| Doc | Content |
|---|---|
| docs/install.md | profile install (web + dsh-tui) / registry / git / local variants / uninstall / --dump-config verification |
| docs/configuration.md | full fallbacks namespace reference, selector syntax, example YAML, plugin-config card usage, TUI readback, behavior notes, preset roles |
| docs/consumer-api.md | developer consumption contract: library API + named llm-fallbacks service + role seeds, export inventory, lifecycle, typing |
| docs/release.md | release process: Trusted Publishing setup, Release prep SOP, fragment format, rollback |
| docs/verification.md | verification records (test matrix, bundle layer order, runtime contracts, QA gate script) |
License
Released under the MIT License — see LICENSE. The LICENSE file is authoritative for copyright and license terms.
Read the usage guide →
Install steps, key points, FAQ and compatibility for this plugin — auto-derived from indexed fields.
Listing badge
[](https://deepseek-plugin.org/plugins/btspoony/dsh-llm-fallbacks)Paste this markdown into your GitHub README to link back to this listing. The badge only states the listing — not a security endorsement.