refactor(kilo-console): remove duplicate remote MCP normalization - #13653
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Reviewed by grok-4.6 · Input: 68.5K · Output: 3.5K · Cached: 126.3K Review guidance: REVIEW.md from base branch |
marius-kilocode
enabled auto-merge
September 1, 2026 10:20
iscekic
approved these changes
Sep 1, 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
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.
What Problem This Solves
MCP marketplace normalization has two adjacent branches with identical remote-config handling. The first checks type=remote plus a string URL; the second accepts any string URL.
Why This Change Was Made
Delete the narrower duplicate branch. Its inputs now reach the identical broader branch. Local command-array handling remains first, so its precedence is unchanged. Headers, OAuth, enabled state, timeout, and fallback behavior remain unchanged.
User Impact
No intended behavior change. Explicit remote and URL-only marketplace entries use the same existing normalization path.
Evidence