lookup

Code intelligence routing directs symbol, type, or API questions to the most suitable analysis tool—such as LSP, ast-grep, Context7, or octocode—determining whether to inspect definitions, structural patterns, or external docs before you start searching.

Routing code-understanding questions to the right tool avoids wasteful grep-and-doc cycles by returning a deterministic decision on whether to use LSP for types, ast-grep for structural patterns, Context7 for external docs, or octocode for public code search.

Yes, routing operates across all languages supported by LSP, directing symbol detail queries to LSP hover and go-to-definition features while routing structural pattern matching to ast-grep and external API documentation to Context7.

Routing local versus external code questions selects the appropriate tool based on context, directing local symbol and definition inspections to LSP, structural patterns to ast-grep, and external library documentation to Context7 or public code search to octocode.

Use ast-grep for identifying structural code patterns, while reserving LSP for resolving specific symbol types, hover details, and go-to-definition queries based on the routing decision provided for your code-understanding question.

No, code routing returns a deterministic routing decision identifying the most suitable analysis tool without executing the target tool, leaving the actual code search, symbol inspection, or documentation retrieval to be performed separately.