Where it comes from
Your agent draws it during onboarding. It reads your repos, proposes two to four districts and a handful of modules, ties each one to files it actually saw, and shows you the list before saving. You approve names you would use — “Shift store”, not “Backend”. Nobody draws boxes by hand, and nothing is invented: a module that claims files has files.Reading it
- Modules are the parts of your system, grouped into districts. The outer ring is everything external you depend on.
- Edges are the connections between them, typed:
HTTP,MCP,OTEL,WS,DEP. - Tiers separate a service from a library, from a tool you run locally, from something outside your control.
Peel it back until it answers one question
Behind the gear, every connection type and every module tier toggles on and off. A map showing everything at once shows nothing — turn layers off until only the question you are asking is left. Your choices persist between sessions. The same gear has While you were away. Leave it on and the morning summary opens when there is something new. Turn it off and the summary stays quiet until you ask for it. This is the same switch as in project map settings. Hover or click a module and only its edges label themselves, so you get the local picture without the global clutter.Ask a building what it does
Click any module for what it is, what it connects to, which files belong to it, and what is happening inside it right now. Ask a question there — “what is this for?”, “what breaks if I change it?” — and the answer comes back from that module’s real files and records, with which ones it read. This is the fastest route into an unfamiliar part of a system, including your own six months on.Bottom left
Agent queue opens the same queue as on the project map. Telemetry is on the map so the corner stays familiar. Opening it in the beta says it is not currently shipped. There is no live agent feed behind that button yet.Flows and the walkthrough
- Flows are stories of how data actually moves through your system, played out across the map rather than described in a paragraph.
- The walkthrough is a guided first tour. Dismiss it any time; it does not come back uninvited.
Recent work lights it up
Once your agent is connected, every commit it records is matched to your modules by the files it touched. A module worked on recently reads as active; one worked on today reads as fresh. Over a week the map shows where your effort actually went, which is not always where you thought it went.Beta maps do not yet redraw themselves as your code drifts. If a repo changes shape substantially, ask your agent to update the map.