Skip to content

fix(indexing): improvements to semantic_search tool description #12227

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
marius-kilocode merged 1 commit into from
Jul 31, 2026
Merged

fix(indexing): improvements to semantic_search tool description #12227

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions packages/opencode/src/kilocode/tool/semantic-search.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,11 +2,9 @@ Find code snippets by semantic meaning and return ranked matches with file paths

## When to use

- Explore an unfamiliar code area before you know exact identifiers
- Find related implementations of a concept or behavior across the workspace
- Search by intent such as authentication, caching, or session resume logic
- Narrow a large codebase before following up with `Read` or `Grep`
- Limit semantic search to one subdirectory with `path`
Use early for open-ended exploration when you know the intent
but not the exact identifiers or the semantics. Once likely files or symbols are found,
follow up with Grep and Read. Prefer Grep directly when exact terms are already known.

@kilo-code-bot kilo-code-bot Bot Jul 31, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUGGESTION: Keep tool names in backticks for consistency

Every other tool reference in this description is code-formatted (Grep, Glob, Read, path), but the new prose mentions Grep and Read as plain words. Since this text goes straight into the model-facing tool description, consistent formatting makes it clearer these are literal tool names rather than prose.

Suggested change
follow up with Grep and Read. Prefer Grep directly when exact terms are already known.
follow up with `Grep` and `Read`. Prefer `Grep` directly when exact terms are already known.

Reply with @kilocode-bot fix it to have Kilo Code address this issue.


## When NOT to use

Expand All @@ -25,4 +23,5 @@ Find code snippets by semantic meaning and return ranked matches with file paths
## Constraints

- Write the query in English.
- Use `path` only for subdirectories inside the current workspace.
- Searches the entire current workspace by default. Limit semantic search to one subdirectory with `path`.
- Cannot search outside the current workspace. Use other tools if this functionality is needed.
Loading