Skip to content

fix(kilo): use @ai-sdk/openai-compatible instead of opencode-kilo-auth#939

Merged
rekram1-node merged 1 commit intoanomalyco:devfrom
Nomadcxx:fix/kilo-npm-provider
Feb 17, 2026
Merged

fix(kilo): use @ai-sdk/openai-compatible instead of opencode-kilo-auth#939
rekram1-node merged 1 commit intoanomalyco:devfrom
Nomadcxx:fix/kilo-npm-provider

Conversation

@Nomadcxx
Copy link
Contributor

Fixes the Kilo provider npm field from opencode-kilo-auth to @ai-sdk/openai-compatible and adds the api endpoint.

The bug: The current npm = "opencode-kilo-auth" causes ProviderInitError: fn3 is not a function in OpenCode because that package is not bundled and does not export a standard create* function (ref).

The fix: @ai-sdk/openai-compatible is already bundled in OpenCode and works with the Kilo gateway. Added api field pointing to Kilo endpoint, matching other OpenAI-compatible providers (deepseek, together, fireworks-ai, nvidia).

Companion to anomalyco/opencode#13765 (CUSTOM_LOADERS wiring for Kilo).

The npm field pointed to opencode-kilo-auth which causes
ProviderInitError when loading Kilo models.

Switched to @ai-sdk/openai-compatible (already bundled in OpenCode)
and added api field for the gateway endpoint.
@rekram1-node rekram1-node merged commit 756fb77 into anomalyco:dev Feb 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants