fix(vscode): improve autocomplete error messages to cover BYOK and credits scenarios#11602
Merged
Merged
Conversation
Contributor
Code Review SummaryStatus: 1 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Fix these issues in Kilo Cloud Files Reviewed (2 files)
Previous Review Summaries (3 snapshots, latest commit 3f3b8a4)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 3f3b8a4)Status: 1 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Fix these issues in Kilo Cloud Files Reviewed (42 files)
Previous review (commit ad830ab)Status: 1 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Fix these issues in Kilo Cloud Files Reviewed (22 files)
Previous review (commit 17d00b6)Status: 1 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Fix these issues in Kilo Cloud Files Reviewed (2 files)
Reviewed by gpt-5.4-20260305 · Input: 50.7K · Output: 5.4K · Cached: 209.4K Review guidance: REVIEW.md from base branch |
…edits scenarios Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
3f3b8a4 to
e7db09e
Compare
chrarnoldus
approved these changes
Jun 29, 2026
vkeerthivikram
pushed a commit
to vkeerthivikram/kilocode
that referenced
this pull request
Jun 30, 2026
…r-messages-byok-credits fix(vscode): improve autocomplete error messages to cover BYOK and credits scenarios
NJ-2020
pushed a commit
to NJ-2020/kilocode
that referenced
this pull request
Jul 4, 2026
…#11602) Co-authored-by: Brendan Allan <brendonovich@outlook.com>
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
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.
Summary
Context
When autocomplete fails with a 402, 401, or 403 error, a VS Code warning popup is shown. Previously:
The gateway (
kilo-gateway.ts) returns 401 for both missing Kilo auth and BYOK key resolution failures. It passes through 402 from upstream providers when quota is exhausted — whether that's Kilo's gateway or a BYOK provider. The VS Code client (AutocompleteServiceManager.ts) maps these to user-visible messages without knowing which underlying cause triggered them, so both causes must be described.Changes
Only
packages/kilo-vscode/src/services/autocomplete/i18n/en.tsis changed — this is the sole source of autocomplete error strings (the autocomplete i18n system only has an English file; no other language files exist for these keys).Built for Mark IJbema by Kilo for Slack