Project Map

Project Map is not a third making mode. Open it from the top-right map control or press M; closing the lens returns to the previous Build task, Design state, or project home.

What it shows

• your pages, labelled by URL — with badges when two files serve the same address through different route groups or parallel slots;
• product areas as containers that open on double-click, so a large app discloses progressively instead of rendering thousands of cards;
• derived connections as toggleable layers: the URL hierarchy (always exact), literal navigation links, page-to-component imports, and API calls;
• planned nodes you draw beside the observed ones, connectable to real pages, with hand-editable specs;
• archives and non-code trees as labelled containers — a folder with no app routes says so plainly instead of showing an empty canvas.

Repository intelligence

The desktop scanner reads the bound workspace statically — no model calls, no tokens, live via a file watcher. A folder holding several apps or versions splits into one area per app root, each with its own URL space. The cloud project retains a capped read-only snapshot so collaborators see the map without a bound workspace, and an open map offers a reload chip when someone saves a newer version.

Working from a node

Selecting a node opens its details: repository facts, exported symbols, a hand-editable spec, open-in-Finder and open-file on desktop, the tasks already linked to this node, and task delegation that carries the node as an explicit context ref. Connected engines can read the map over MCP and propose changes back with the update_architecture tool — proposals land pending on the map for per-item accept or dismiss, and never mutate the accepted plan directly.