Skip to content

Upstream request failed: [404] No allowed providers available for selected model despite provider.only whitelist #45995

Closed as not planned

Description

@dancowwwwwwww

Description

Summary

When using a model via Console (Models.dev), opencode fails with a 404 'No allowed providers are available for the selected model' error. Even though the selected model IS among the served providers, the provider.only preference whitelists a provider that does not actually serve the model, so every request fails.

Error

Error from provider (Console): Upstream request failed: [404] No allowed providers are available for the selected model. Providers serving xiaomi/mimo-v2.5-20260422: gmicloud, deepinfra, xiaomi, parasail, streamlake, novita, but your request's provider.only preference permits only: tencent.

[retrying in 4s attempt #3] Retry Error

Expected behavior

opencode should either (a) fall back to one of the providers that actually serves the selected model, or (b) surface a clearer, actionable error instead of retrying the request 3+ times with a 404. The current behavior hides the root cause (an incompatible provider.only preference vs. the model's actual providers) behind a generic retry loop.

Plugins

No response

OpenCode version

No response

Steps to reproduce

  1. Select model xiaomi/mimo-v2.5-20260422 (served by gmicloud, deepinfra, xiaomi, parasail, streamlake, novita).
  2. Set a provider.only preference that whitelists only 'tencent' (a provider that does NOT serve this model).
  3. Send a message.
  4. Observe repeated 404 errors with retry loop: '[retrying in 4s attempt feat: model config persistence #3]'.

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

Windows Terminal

Activity

  1. github-actions commented on Aug 28, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

  2. aentrepreneur commented on Sep 3, 2026

    @aentrepreneur

    Tengo el mismo error (misma cadena exacta) desde OpenCode CLI 1.18.26 en Linux, usando providerID=opencode (no opencode-go) y modelID=mimo-v2.5-free.

    Contexto

    • Config local (~/.config/opencode/opencode.json): model=opencode/big-pickle, small_model=opencode/hy3-free.
    • No encuentro ninguna configuración local de provider.only/whitelist (no aparece en los configs cargados).

    Log (opencode.log) con timestamps

    2026-08-28T21:20:15.315Z  stream providerID=opencode modelID=nemotron-3.5-lightning-free small=true agent=title
    2026-08-28T21:20:17.846Z  stream providerID=opencode modelID=mimo-v2.5-free small=false agent=build
    2026-08-28T21:20:18.436Z  ERROR stream error providerID=opencode modelID=mimo-v2.5-free agent=build
      AI_APICallError: Error from provider (Console): Upstream request failed: [404] No allowed providers are available for the selected model.
      Providers serving xiaomi/mimo-v2.5-20260422: gmicloud, deepinfra, xiaomi, parasail, streamlake, novita,
      but your request's provider.only preference permits only: tencent.
    (repite en 21:20:21Z, 21:20:26Z, 21:20:36Z)
    

    Metadatos del evento: run=e14f2456, session.id=ses_fb5c15acfffecECMuv3wHQAaPw.

    Esperado

    • Si el backend aplica/inyecta provider.only=tencent, debería no aplicarlo cuando el modelo no es servido por Tencent (o elegir automáticamente un provider válido de la lista).
    • Además, este 404 parece no transitorio: reintentar N veces solo alarga la “sensación de freeze” en build. Sería mejor surfacing un error actionable (incl. dónde viene el provider.only).
  3. Tarquinen commented on Oct 20, 2026

    @Tarquinen
    Member

    Thanks for the report! This was a temporary problem with the model's upstream provider around the time it was reported, and there haven't been new reports here since. If you still see it on the latest OpenCode, please open a new issue with your version, model and the exact error. Closing this issue.

    — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions