Code navigation is the set of editor capabilities that let a programmer move through a codebase by meaning rather than by scrolling through files. Instead of hunting for where a function is defined or every place a variable is used, the developer asks the tool: jump to this symbol’s definition, list everywhere it is referenced, show who calls this method, or search the whole project for a symbol by name. These features are what turn a directory of text files into something that can be explored as a connected program.
The core navigation operations have been standardized by the Language Server Protocol, which defines them as language-agnostic requests between an editor and a language server. The specification describes textDocument/definition, the request behind go-to-definition, which resolves a position in a file to the location where that symbol is declared or defined. It defines textDocument/references, which find-references uses to return every location where a symbol is used. For exploring how code calls itself, the protocol defines textDocument/prepareCallHierarchy together with incoming and outgoing call requests, which power a call hierarchy view.
Symbol search is covered by the same specification through document and workspace symbol requests, which let an editor list the symbols defined in a file or search for a symbol by name across an entire project. Because these requests have a defined shape, an editor can offer the same navigation experience for any language that ships a conforming language server, without the editor itself needing to understand each language’s syntax and scoping rules.
The technical foundation of code navigation is a model of the program’s symbols and their relationships, often built by parsing the source into an abstract structure and resolving names to declarations. Before this was standardized, each integrated development environment built its own language-specific machinery for indexing code, which is why deep navigation was historically available only for the languages a given IDE chose to support well.
By factoring navigation into a protocol, the Language Server Protocol made these features portable. A single language server can give go-to-definition, find-references, and call hierarchy to many different editors at once, which is why modern lightweight editors can offer navigation that once required a heavyweight, language-specific IDE.