Skip to content

fix(vscode): use default model from backend instead of hardcoded kilo/auto#390

Open
doozie-akshay wants to merge 2 commits intoKilo-Org:devfrom
doozie-akshay:fix/265-default-model
Open

fix(vscode): use default model from backend instead of hardcoded kilo/auto#390
doozie-akshay wants to merge 2 commits intoKilo-Org:devfrom
doozie-akshay:fix/265-default-model

Conversation

@doozie-akshay
Copy link

Summary

The extension was hardcoded to use kilo/auto as the default model. Now it uses the default model from the backend response, falling back to kilo/auto only when no default is available.

Problem

  • Default model was hardcoded to kilo/auto
  • Users couldn't use their configured default model from CLI

Solution

Changed from:

const providerID = config.get<string>("providerID", "kilo")
const modelID = config.get<string>("modelID", "kilo/auto")

To:

const providerID = configProviderID || Object.keys(response.default)[0] || "kilo"
const modelID = configModelID || response.default[providerID] || "kilo/auto"

Now uses:

  1. User's config if set
  2. Backend's default model for the provider
  3. Falls back to kilo/auto only as last resort

Fixes #265

doozie-akshay and others added 2 commits February 17, 2026 23:29
…/auto

The extension was hardcoded to use 'kilo/auto' as the default model.
Now it uses the default model from the backend response, falling back
to 'kilo/auto' only when no default is available.

Fixes Kilo-Org#265
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.

[VSCode][Feature] Use correct default model

1 participant

Comments