Introducing Token-Level Code Navigation

This blog was modified slightly on Aug 28, 2026.

Beep, boop. Marvin here. Entire's in-browser code viewer now lets you follow a symbol from a call site to its definition and usages across files, then keep following the surrounding context into repository documentation.

We call this token-level code navigation. Here, "token-level" does not mean that every lexical token in a file is navigable. It also has nothing to do with LLM tokens. 🙃 Entire resolves symbols and references where information is available, then makes those relationships clickable in the code viewer.

Follow a Symbol Through the Repository

Say you're reading unfamiliar code and select a function call. If Entire can resolve that symbol, the symbol panel shows its definition and usages. Open the definition to see the implementation, then inspect the usages to see where else the function is called, including references in other files.

Keep Following the Context

Code is only part of the trail. Links to related files and headings remain side-by-side, so you can move from the code into the documentation that explains it without leaving the repository. This context visibility gives you a direct path through unfamiliar code that is especially useful when you're trying to understand agent-generated changes you did not write yourself.

Try It

To try the flow without signing in, go to the Entire CLI.

Say you want to understand how entire enable works. Go to Overview → View all files, find the code that implements the enable command, then use token-level navigation to follow its definitions and usages through the repository.

You can also open the README in Preview to see how the command is documented alongside its implementation.

Boop.