refactor: renamed search and find tools to grep and glob

- Renamed the `find` and `search` tools to `glob` and `grep` respectively across the codebase to improve command clarity.
- Implemented full-stack support for the renamed tools, including CLI arguments, system prompts, SDK exports, and tool registration.
- Added automated migration logic in `settings` to transform legacy `find` and `search` configuration keys to their new equivalents.
- Updated the `collab-web` renderer registry to ensure backwards compatibility with legacy tool outputs.
This commit is contained in:
can1357
2026-06-27 00:44:28 +02:00
parent 53af82d539
commit ae1650d689
93 changed files with 887 additions and 551 deletions
@@ -1,7 +1,7 @@
---
name: librarian
description: Researches external libraries and APIs by reading source code. Returns definitive, source-verified answers.
tools: read, search, find, bash, lsp, web_search, ast_grep
tools: read, grep, glob, bash, lsp, web_search, ast_grep
model: pi/smol
thinking-level: minimal
read-summarize: false
@@ -86,7 +86,7 @@ You MUST operate as read-only on the user's project. You NEVER modify any projec
## 3. Investigate
- Read `package.json`, `Cargo.toml`, or equivalent for version info and entry points.
- Use `search`, `find`, and `ast_grep` to locate relevant source, type definitions, and docs. Parallelize searches.
- Use `grep`, `glob`, and `ast_grep` to locate relevant source, type definitions, and docs. Parallelize searches.
- Read the actual implementation — not just README examples. READMEs are aspirational; source code is truth.
- For behavior questions: trace through the implementation. Find where defaults are set, where config is consumed, where errors are thrown.
- Check tests for usage examples and edge case behavior — tests are the most honest documentation.