Search the codebase knowledge base for facts about what the code does, how it's built, and what it assumes.

Use this FIRST before reading source files. It returns pre-extracted facts ranked by relevance, saving significant time and tokens.

MULTI-QUERY: Use semicolons to search multiple keyword groups in one call. Example: "payment gateway; checkout flow; stripe webhooks" This runs 3 searches, deduplicates, and returns combined results. ALWAYS batch related searches into one call — this is dramatically cheaper.

Args: query: Search keywords (e.g. "authentication", "payment flow", "database connection") Use semicolons to batch multiple searches: "auth login; session JWT; middleware" category: Optional filter — "behavior" (what it does), "design" (how it's built), or "assumption" (what it expects) min_confidence: Minimum confidence threshold 0.0-1.0 (default: 0.0) limit: Max results per query (default: 20). With batched queries, total results can be up to limit × number of queries (max 65). repo_name: Optional filter to scope search to a specific repository

Get all extracted facts for a specific module.

Module IDs look like "SCAN:backend/app/api". Use search_codebase first to discover module IDs, then use this for a deep dive into a specific module.

Args: module_id: The module identifier (e.g. "SCAN:backend/app/api/simplified")

Get the most recently extracted facts across the entire codebase.

Useful for understanding what changed recently or getting an overview of the codebase.

Args: category: Optional filter — "behavior", "design", or "assumption" limit: Number of recent facts to return (default: 10)

Find all modules and PRs where a specific component (file/service) appears.

Use this to understand the blast radius of changes to a component — what depends on it and what it depends on.

Args: component_name: File path or service name (e.g. "api_service.py", "backend/app/auth")

List scanned modules in the knowledge base.

Without repo_name: returns a compact summary of repos with module/fact counts. With repo_name: returns the full list of modules for that specific repo.

Always call without repo_name first to discover available repos, then call again with repo_name to get the module list for a specific repo.

Args: repo_name: Repository name — pass this to get the full module list for one repo

Get cross-repo dependency graph showing which repos depend on each other.

Use this to understand the blast radius of changes across repositories. Data comes from package manifests (go.mod, package.json), not code analysis.

Args: repo_name: Filter to a specific repo. Without this, returns entire graph. direction: "outgoing" (what this repo depends on), "incoming" (what depends on this repo), "both"