Skip to main content

Search

Search works best when you move from precise scope to precise evidence: file discovery first, then lexical or hybrid search, then bounded file reads.

localnest_search_files​

Best first step when looking for a feature or module by name.

Use when

Start here for folders, modules, subsystems, acronyms, and other path-oriented discovery tasks.

localnest_search_code​

Use for exact identifiers, imports, symbols, or regex patterns.

Useful parameters:

  • glob
  • max_results
  • case_sensitive
  • context_lines
  • use_regex

Use when

Choose this tool when you already know the symbol, error text, or pattern you want to match.

localnest_search_hybrid​

Use for concept-level retrieval when exact keywords are not enough.

Useful parameters:

  • project_path
  • all_roots
  • min_semantic_score
  • auto_index

Use when

Use hybrid search after indexing when you need semantic recall, architecture context, or concept-level lookup.

localnest_get_symbol​

Use for definition/export lookup when you know the symbol name but not the file.

localnest_find_usages​

Use for import/call-site lookup when tracing symbol usage.

1
Find the likely area

Run localnest_search_files to narrow the search to a directory, feature, or component.

2
Search with the right mode

Use localnest_get_symbol/localnest_find_usages for symbol tracing, localnest_search_code for exact terms, and localnest_search_hybrid for concepts.

3
Confirm with file reads

Validate the result set with localnest_read_file before drawing conclusions or editing code.

Fast mode defaults​

For lowest latency in daily use:

  • Pass project_path whenever known.
  • Start with max_results in the 20-40 range.
  • Use context_lines=2 in localnest_search_code.
  • Keep all_roots=false unless cross-repo search is required.
  • Use localnest_search_hybrid only when exact lexical search is not enough.
  • Keep reranker disabled (use_reranker=false) until a final precision pass is needed.