Ask the codebase a question. No model. No API key.

1. 01Atlas

   First hour in a new codebase

   Ask in plain words, in the editor’s Atlas view or on the command line. The answer is a flow: the files involved in columns from left to right, entry points first, the core files as cards with their key symbols, and tests left out until you ask for them. The graph is built from tree-sitter parses of Go, TypeScript, JavaScript, Python, Java, Kotlin, C, C++ and C#, so the answer is callers, files and the subsystem they belong to, not a guess. The flow comes from the graph alone; with a model set up for the branch, Atlas also writes a short walkthrough and names each step.

2. 02Atlas

   Before you edit, see what breaks

   Affected answers the symbol question; impact answers the branch question: what this branch’s changes touch versus a base, down to public entry points and the suites that gate them. In the Atlas view one switch moves any answer between its flow and the map, where the same answer lights up across the whole branch, with every caller and callee one click from its code.

3. 03Atlas

   The agent’s loop: ask before editing

   The coding harness gives agents Atlas as tools, and a hook steers an external agent from grep to the graph. A query returns a token-budgeted subgraph, so the context window goes to the right code, and the agent’s first move on a task is the same as a careful engineer’s.

4. 04Atlas

   Across projects, without cloning

   Point a query at another project and branch through the control plane. The graph is served on every branch server, in the editor’s Atlas view, and exports as an interactive map or a wiki with one article per subsystem.

Coming soon: model-backed extraction of documents is optional and opt-in; code never needs it

The full reference lives in the docs.