ProviderInitError: ProviderInitError

[I4mCh40s]

Plugin Type

CLI Tool

App Version

1.0.21

Description

After trying to queue the command (after pc slept and woken up) it shows "ProviderInitError: ProviderInitError " using any mode, and a free model. Tried with GLM5 and Minimax M2.5 :((

Reproduction steps

Open Kilo CLI and queue any command in a preexisting project.

Provider

Kilo Code

Model

GLM-5

System Information

No response

[marrov]

I can confirm! Came here to write the same thing, it looks like this is happening for all models.

Edit: OP mentions VSCode extension, but I have the same issue in the Kilo CLI.

[jhartum]

got same problem

[I4mCh40s]

I can confirm! Came here to write the same thing, it looks like this is happening for all models

Phew, its not just me then

[ElYaiko]

Same

[Aliman00]

Same here using kilo cli.

[marcd35]

same issue. windows 10. only the CLI seems to be affected - the VSCode extension works fine.
Attempted fix: deleting the .local\share\kilo folder and reinstalling the CLI via terminal does not fix issue

[DoubyCz]

The models API returns "npm": "opencode-kilo-auth" for the kilo provider, but this is an auth plugin with no SDK factory function. The getSDK() function can't find a create* export → undefined → fn3 is not a function.

Fix: The models API should return "npm": "@kilocode/kilo-gateway" for the kilo provider — this matches the BUNDLED_PROVIDERS key in packages/opencode/src/provider/provider.ts (line 71) and contains the createKilo() factory.

For reference, other providers work because their npm fields match bundled keys correctly (@ai-sdk/anthropic, @ai-sdk/openai, etc.).

[Noktomezo]

It seems like they fixed it, update your Kilo, guys (1.0.21 -> 1.0.22)

[erik777]

It's the anthropic auth bricking us all according to ChatGPT. GPT, based on npm analysis, said there were also rapid fire updates today to kilocode auth. need an update from someone on the inside to help us understand. I can post GPT diagnostics if that helps.

[lambertjosh]

It seems like they fixed it, update your Kilo, guys (1.0.21 -> 1.0.22)

Hi folks, apologies for the interruption this has indeed been fixed. Please update (or restart your CLI if you have auto-update on) and everything should work.

There was a model data change that conflicted with the Kilo Gateway provider which has been fixed: https://github.com/Kilo-Org/kilo/pull/338/changes

[surya-gorla]

@lambertjosh , @Noktomezo Thank you for the information. Got to this discussion after scouring the internet for a while.

[I4mCh40s]

Thanks! All working now!

[github-actions]

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please reopen it or create a fresh new one.