fix(vscode): remove stale speech-to-text setting - #11039
Merged
Merged
Conversation
marius-kilocode
enabled auto-merge (squash)
June 9, 2026 12:18
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Reviewed by claude-4.6-sonnet-20260217 · 290,952 tokens Review guidance: REVIEW.md from base branch |
chrarnoldus
approved these changes
Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The extension manifest still exposes
kilo-code.new.speechToText.enabled, but speech input availability now comes from the connected Kilo provider and profile. Leaving the unused setting visible suggests that it controls behavior when no runtime code reads it.Remove the obsolete enabled setting from VS Code configuration contributions. Keep
kilo-code.new.speechToText.modelintact so model selection and the current provider-based availability behavior remain unchanged.