dsh-llm-fallback

Configuration

The composition entry supplies the base; the llm-fallback section of the user settings document replaces it wholesale on the next failure (no restart):

llm-fallback:
  chains:
    - primary: { provider: z-ai-glm-53-flash }
      fallbacks:
        - { provider: openrouter, model: nvidia/nemotron-3-ultra-550b-a55b:free }
        - { provider: openrouter, model: minimax/minimax-m3:free }
  healOn: [SERVER, TIMEOUT, TRANSPORT, RATE_LIMIT, EMPTY_RESPONSE, INVALID_REQUEST]
  sticky: true

Field	Meaning
chains	Ordered healing chains; an empty list keeps the plugin dormant.
chains[].primary	The watched route. model absent watches every model on the provider route.
chains[].fallbacks	Ordered targets; each needs provider and model, with an optional reasoningEffort (off/low/high/max).
healOn	Failure codes that trigger a heal; anything else delegates downstream.
sticky	true keeps the heal for the agent's remaining life; false re-binds the agent's own route when the healing turn closes.

A malformed section is refused where it is written — the settings write fails with the offending chain and field named.