@arcships/dsh-llm-aimux

Configuration

Routes are keyed by dsh provider id; each maps to one aimux provider. The composition entry below is only the base layer — users add or edit routes through their settings (web Models page → provider card, or the llm-aimux: section in settings.yaml) and changes apply without a restart:

- insert:
    - id: llm-aimux
      name: '@arcships/dsh-llm-aimux'
      config:
        providers:
          deepseek:                    # dsh route id
            provider: deepseek         # aimux provider name (default: the route id)
            apiKeyEnv: DEEPSEEK_API_KEY # credential ref (default: 
_API_KEY)
          kimi:
            provider: moonshot         # credential ref derives as MOONSHOT_API_KEY
          groq:
            displayName: Groq

The same shape works in the user settings layer:

llm-aimux:
  streamIdleTimeoutMs: 300000     # chunk-idle watchdog relayed to aimux
  providers:
    groq: {}
    relay:                        # endpoint override through a gateway/relay
      provider: deepseek
      baseUrl: https://relay.example/v1
      headers:
        X-Org: acme

• provider — an aimux provider name. aimux ships 325+ (251 of them OpenAI-compatible registry entries); see the aimux provider docs.
• Every route appears as a configurable provider on the Models page (ctx.llm.registerConfigurableProviders, addressed at llm-aimux.providers.); added or removed routes swap atomically.
• Credentials resolve through the harness ctx.credentials seam when mounted; otherwise aimux falls back to the provider's own env var. Resolution is per-request, so a rotated key reaches the next call.