Search & code intelligence

Search by what you know

ctx_search consolidates regex, semantic and symbol paths. A regex uses pattern; semantic retrieval uses query; a symbol lookup uses name or a returned handle. These are distinct actions.

{"name":"ctx_search","arguments":{"action":"semantic","path":".","query":"where authentication is checked","top_k":5}}

For exact names, prefer a symbol or regex search. Semantic results depend on index contents and the configured retrieval backend.

Use the indexing guide to inspect or build lexical, graph and semantic indexes. It also distinguishes embedding-runtime setup from a managed triage model.

In the current source contract, ctx_search is read-only. Build or rebuild indexes through ctx_index; the former ctx_search action reindex is no longer accepted.

Inspect relationships

Use the graph and callgraph surfaces for available dependencies, callers, callees and traces. Impact analysis can suggest what to inspect or test after a change.

Static extraction is not a complete model of runtime behavior. Dynamic imports, generated code and unsupported language constructs can leave gaps.

Move from structure to source

A repo map or outline is a navigation aid. Follow its file and symbol locations into the actual implementation, then run the project’s relevant checks.

Refactoring operations can mutate source and may require an IDE/LSP integration. Review their preconditions, expected hashes and preview results before applying them.

Sources & versions3 references · Reviewed 17 Sept 2026

• dynamic_tools.rsrust/src/server/dynamic_tools.rsGitHub
• ctx_search.rsrust/src/tools/registered/ctx_search.rsReviewed checkout
• 04-code-intelligence.mddocs/reference/04-code-intelligence.mdGitHub

Core checkout

0ce2207ee4

Installed runtime

3.10.2

SDK release

1.1.0

Separate baselines for source, CLI/configuration and SDK contracts. Review does not certify every platform or integration.

Versions & compatibility