mirror of
https://github.com/DeusData/codebase-memory-mcp.git
synced 2026-11-12 09:47:20 +08:00
Martin Vogel
8bcb308e28
The human side of the Atlas program: - Overview: the first read of a project — header numbers, region cards with provenance and cohesion, hubs by fan-in, entry points, surprising couplings with enumerated reasons, suggested questions with a why, and the cross-package boundary table. Assembled client-side from the read-only /rpc surface (get_architecture format:json) + the regions payload; no new server code. - Modules: a squarified treemap (in-house, no new dependency) of any folder via /api/tree — sized by symbols, colored by dominant region, hatched where the indexer missed files, breadcrumbed drill-down, file panel listing symbols via search_graph. - Symbol: one page per node via /api/symbol — docstring, flags, region, editor/GitHub links, code on demand, callers/callees with true totals and per-type confidence badges (resolved / reference / unproven), tests, co-change partners, near-clones. - Flows: the /api/flows journeys grouped across/within regions, each a clickable indented call tree with truncation stated, mermaid export. - Changes: detect_changes on the working tree grouped by risk, blast radius citable into the prompt in one click. - ⌘K: symbols (search_graph) + code text (search_code) in one box. - Prompt composer: a basket of cited symbols/regions/flows/questions that renders a prompt naming exact qualified names, file:line ranges and the MCP calls that reproduce the context — the bridge back to the agent. Routing carries every screen in the URL (tab, project, path, sym, flow, node, region) so all of it deep-links. Fixed en route: the /api/flow route pattern '/api/flow?*' never matched (req->path has no query string) — now exact, pinned by a wired-routes test that distinguishes a matched route's 400 from the static handler's 404. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>