Repository navigation
Minimax use fails #40
Description
Unfortunately #39 has not been fully fixed.
I got the question for the api key and the logs say it worked:
[dev:backend] [2025-12-30T22:22:54.505Z] [INFO] Set credentials for provider: minimax
But when I send any prompt, the result is again:
[dev:backend] 906 | const provider = s.providers[providerID]
[dev:backend] 907 | if (!provider) {
[dev:backend] 908 | const availableProviders = Object.keys(s.providers)
[dev:backend] 909 | const matches = fuzzysort.go(providerID, availableProviders, { limit: 3, threshold: -10000 })
[dev:backend] 910 | const suggestions = matches.map((m) => m.target)
[dev:backend] 911 | throw new ModelNotFoundError({ providerID, modelID, suggestions })
[dev:backend] ^
[dev:backend] ProviderModelNotFoundError: ProviderModelNotFoundError
[dev:backend] data: {
[dev:backend] providerID: "minimax",
[dev:backend] modelID: "MiniMax-M2.1",
[dev:backend] suggestions: [],
[dev:backend] },
[dev:backend]
[dev:backend] at getModel (src/provider/provider.ts:911:13)
[dev:backend]
Activity
viraptor commentedon Dec 30, 2025
If I put the key in
MINIMAX_API_KEYenv var, this works. So somehow the key set through the UI does not propagate properly.Fix provider API key storage to match OpenCode schema
fix minimax use (#44)
fix minimax use (chriswritescode-dev#44)