Which directory is codenav navigating, and why? Use when results look like they come from the wrong checkout/worktree.

Get type/documentation info for the symbol at a position.

line and column are 1-indexed. column is a UTF-16 character offset on the line (not a visual/display column): a leading tab counts as one character.

Go to the definition of the symbol at a position.

line and column are 1-indexed. column is a UTF-16 character offset on the line (not a visual/display column): a leading tab counts as one character.

Resolves through ty's type inference, so this works even when the call site only has a typed parameter/attribute (e.g. services.some_method() where services: AppServices is a constructor argument), not just direct references to a name in scope.

Find all usages of the symbol at a position across the workspace.

line and column are 1-indexed. column is a UTF-16 character offset on the line (not a visual/display column): a leading tab counts as one character.

Search the whole workspace for a symbol by name (class, function, method, etc.).

Use this to find a symbol's file/position first, then pass that position to definition/references/hover for precise, type-resolved navigation. Returned positions point at the identifier name (not the class/def keyword) and use the same character-offset column convention as the other tools. Results include a SymbolKind label and are capped. name is accepted as an alias for query. Narrow broad queries with kind (SymbolKind labels, comma-separated: class, function,method, interface, ...) and path (workspace-relative prefix such as src/, or a glob such as src/**/*.py). Production code ranks before tests. Loose fuzzy hits whose names don't contain the query are summarised as a count when real matches exist; pass fuzzy=true to list them too.

Get ty's type-check diagnostics (errors/warnings) for a single file.

What is X and where is it used? Example: symbol_info(name="UserService.create_user").

One-call summary for a name: header, hover text, definition, and references grouped by file — the usual first lookup instead of chaining search_symbol → hover → definition → references by hand.

name is a symbol name, or a dotted Class.method to resolve a specific method when the plain name is ambiguous. Pass file_path (relative to the workspace root) to disambiguate when several symbols share a name elsewhere in the workspace; if it's still ambiguous, the candidates are listed back so you can retry with a narrower name or file_path. query is accepted as an alias for name.

What's in this file? Example: outline(file_path="src/app/services.py").

Indented outline (classes, methods, functions, with line numbers) of a Python file, so you can navigate a large file without reading it in full. Follow up with hover/definition/references at a listed line, or symbol_info by name.

Who calls this function? Example: callers(name="create_user").

Narrower than references, since it leaves out imports and type-only usages and only lists actual call sites.

name resolves the same way as symbol_info (dotted Class.method accepted; pass file_path to disambiguate a common name). query is accepted as an alias for name.

Find concrete classes that structurally satisfy a Protocol port.

Many hexagonal codebases define ports as Protocols that adapters never subclass explicitly, so ty's own implementation/typeHierarchy return nothing for them. This scans classes under SOURCE_ROOT (the whole workspace by default; see CODENAV_MCP_SOURCE_ROOT) whose method names cover the protocol's, then verifies each candidate with ty's real type checker via an in-memory probe file (never written to disk) — so a result means "assignable", not just "same method names". port_name must itself resolve to a Protocol class; other classes' subclasses are better found with references/symbol_info. name and query are accepted as aliases for port_name. file_path narrows the port lookup to one file when the name exists in several. Members inherited from same-workspace base classes, and fields/properties declared by the port, count when matching names. Directories listed in CODENAV_MCP_EXTRA_SOURCE_ROOTS (e.g. tests) are scanned too; their matches (test doubles) are listed under a separate heading.