chore: remove codesearch tool - #11086
Merged
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge The PR cleanly removes the
Files Reviewed (24 files)
Fix these issues in Kilo Cloud Reviewed by claude-4.6-sonnet-20260217 · 927,386 tokens Review guidance: REVIEW.md from base branch |
chrarnoldus
approved these changes
Jun 10, 2026
marius-kilocode
enabled auto-merge
June 10, 2026 16:38
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
chore: remove codesearch tool
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.
OpenCode removed the experimental
codesearchtool, but Kilo retained its implementation and Kilo-specific registration after the merge. That leaves an unsupported tool in the runtime and keeps permissions, settings, and documentation out of sync with upstream.Remove the executable tool and its agent grants, permission handling, tests, settings control, and documentation. Web search remains available as its own permission, while existing client renderers and labels stay intact so historical sessions containing code-search calls continue to display correctly.