Hybrid semantic + lexical search over the indexed code and docs. Describe what the code does in plain words ('method that clamps camera zoom'), not an identifier. Returns ranked chunks with file:line, symbol and score; a hybrid score near 0.03 is a strong match. Omit source to search every source at once. outline=true returns signatures only, for cheap triage of broad queries.

Escalation for when search came back weak or empty: runs 2-4 genuinely different phrasings of the same need and returns the first set that passes the quality threshold, or the strongest weak set with a warning. Slower than search; do not start here.

List which sources exist and what each one is: name, type, path, chunk count and drift flag. Read from config and metadata, no index opened. Call it first when you do not know the source names a source argument expects; for how fresh one index is, and whether to rebuild it, use get_rag_status instead.

Force a full rebuild of a source's index. Expensive and blocking; the watcher keeps the index current, so use it only after a big merge or a drift warning.

Index state for one or all sources: freshness, chunk count, last update, drift. Check it before considering a rebuild.

Report that the index could not answer you, before giving up. Appended to a local log (never uploaded) so the index owner can tune sources and filters.

Raw access to the code knowledge graph (calls, inheritance, imports), for the questions the dedicated tools do not cover: find_usages, impact and describe_symbol answer the common ones with the results already shaped. operation: callers | callees | subclasses | superclasses | imports | neighbors | shortest_path | overview | surprising_connections | status. symbol is matched as a case-insensitive substring; results carry file:line.

Jump to where a symbol is defined, when you already know its name. AST-precise when the graph layer is on, BM25 fallback otherwise; each hit says which. Use search instead when you can only describe what the code does, and describe_symbol when you also want the callers and the tests in the same call.

Every use of a symbol: calls (from the graph when on) plus textual references (generics, decorators, imports, docs), definition excluded. Answers 'who uses X' at one hop; impact walks the chain further and adds the tests.

List the tests that mention a symbol, searched under conventional test paths (tests/, spec/, tests/, _test., .spec., *Test.cs, *Tests.cs); test_path_pattern replaces them for another layout. Use it when the tests are all you want, before or after a change; describe_symbol returns the same tests bundled with the definition and the callers, and impact returns them for a whole blast radius.

Code semantically similar to a snippet you already have, dense search only: use it before writing a function, to check whether something like it exists. search is the one to call when you can describe the need in words instead. Snippets are cut at 2000 chars.

One-shot context for a symbol: definition, who calls it, what it calls, and its tests, in a single call. The fastest way to understand a function or class before changing it, and cheaper than find_definition, find_usages and find_tests_for one after the other. Call data needs the graph layer; definition and tests always work.

Answer 'what breaks if I change this': everything that reaches a symbol transitively through the call graph, with hop distance, plus the tests to re-run. Use find_usages for the direct, one-hop answer; use this before a risky edit, when the indirect callers are the point. max_depth trades reach for noise: 2 stays close to the change, 6 on a hub symbol can return most of the codebase. Transitive callers need the graph layer.

Orientation for an unfamiliar codebase: languages by file count, frameworks, manifests, likely entry points, and build/test/run commands. Filesystem scan, no index needed. Call once per session.

A file as a unit: the symbols it defines, what it imports, and which files depend on it (via the call graph). Read it before editing a file you don't know; repo_overview does the same for the whole repository, and describe_symbol for one symbol inside the file.

Write a self-contained offline HTML view of a symbol's blast radius (mode=symbol) or a file's imports and dependents (mode=module), for a human to open or attach to a PR. Returns the file path.