You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pkg/config/auto.go's DefaultModels["fireworks"] and examples/fireworks.yaml both reference:
accounts/fireworks/models/kimi-k2-instruct
This model ID does not exist in the fireworks-ai catalog on models.dev — and, as far as I can tell from both the current and previous embedded pkg/modelsdev/snapshot.json, it never has. models.dev's naming for this lineup uses a different scheme entirely (e.g. accounts/fireworks/models/kimi-k2p6, .../kimi-k2p7-code, .../kimi-k3).
Also referenced (with the same staleness) in:
pkg/config/auto_test.go (two assert.Equal checks mirroring the value in auto.go, not validated independently)
docs/providers/fireworks/index.md (model: snippets ×4, plus a stale "Available Models" table listing accounts/fireworks/models/kimi-k2-instruct, .../llama-v3p3-70b-instruct, .../qwen3-235b-a22b — none of which exist in the current fireworks-ai catalog; Llama has no successor there at all anymore)
Why it's invisible to CI
pkg/config/examples_test.go maintains a modelsDevAbsentProviders map that skips models.dev catalog validation entirely for several providers, including fireworks, with the comment:
"fireworks": true, // models.dev catalogs Fireworks under the "fireworks-ai" id, not "fireworks"
This is accurate — but the consequence is that no test anywhere ever checks that the model string configured for the fireworks provider actually exists, so this reference has silently drifted (or was simply wrong from the start) without any CI signal. The same blind spot applies to the other skipped providers (together, moonshot, chatgpt, ovhcloud, vercel, opencode-zen, dmr, cloudflare-workers-ai, cloudflare-ai-gateway), though this issue is specifically about the concrete Fireworks breakage found.
Suggested fix direction
Update the stale references to a model that currently exists in the fireworks-ai catalog (e.g. accounts/fireworks/models/kimi-k3) — tracked separately as part of the broader model-reference refresh for PR chore: refresh models.dev snapshot (+79 -75 ~196) #4121.
Longer-term: teach examples_test.go (or a dedicated test) to resolve the actual models.dev catalog id for these "absent" providers (e.g. fireworks → fireworks-ai, together → togetherai, moonshot → moonshotai) instead of skipping validation outright, so this class of staleness gets caught automatically going forward.
What's wrong
pkg/config/auto.go'sDefaultModels["fireworks"]andexamples/fireworks.yamlboth reference:This model ID does not exist in the
fireworks-aicatalog on models.dev — and, as far as I can tell from both the current and previous embeddedpkg/modelsdev/snapshot.json, it never has. models.dev's naming for this lineup uses a different scheme entirely (e.g.accounts/fireworks/models/kimi-k2p6,.../kimi-k2p7-code,.../kimi-k3).Also referenced (with the same staleness) in:
pkg/config/auto_test.go(twoassert.Equalchecks mirroring the value inauto.go, not validated independently)docs/providers/fireworks/index.md(model:snippets ×4, plus a stale "Available Models" table listingaccounts/fireworks/models/kimi-k2-instruct,.../llama-v3p3-70b-instruct,.../qwen3-235b-a22b— none of which exist in the currentfireworks-aicatalog; Llama has no successor there at all anymore)Why it's invisible to CI
pkg/config/examples_test.gomaintains amodelsDevAbsentProvidersmap that skips models.dev catalog validation entirely for several providers, includingfireworks, with the comment:This is accurate — but the consequence is that no test anywhere ever checks that the model string configured for the
fireworksprovider actually exists, so this reference has silently drifted (or was simply wrong from the start) without any CI signal. The same blind spot applies to the other skipped providers (together,moonshot,chatgpt,ovhcloud,vercel,opencode-zen,dmr,cloudflare-workers-ai,cloudflare-ai-gateway), though this issue is specifically about the concrete Fireworks breakage found.Suggested fix direction
fireworks-aicatalog (e.g.accounts/fireworks/models/kimi-k3) — tracked separately as part of the broader model-reference refresh for PR chore: refresh models.dev snapshot (+79 -75 ~196) #4121.examples_test.go(or a dedicated test) to resolve the actual models.dev catalog id for these "absent" providers (e.g.fireworks→fireworks-ai,together→togetherai,moonshot→moonshotai) instead of skipping validation outright, so this class of staleness gets caught automatically going forward.References