productcode & review
Ask the codebase a question. No model. No API key.
Atlas builds a symbol-level graph of the workspace on the branch, groups it into subsystems, and answers plain-language questions with exact files and lines. People use it to onboard; agents use it instead of grep.
how you use it
Atlas, in order.
01
First hour in a new codebase
Ask in plain words, in the editor’s Atlas view or on the command line. 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. Deterministic community detection keeps the subsystems stable from day to day.
02
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 the blast radius lights up on the graph itself.
03
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.
04
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.
not built yet: model-backed extraction of documents is optional and opt-in; code never needs it
The full reference lives in the docs.
works with
Open a branch and try it.
Boots in seconds. Your team joins with a link.