Skip to content

Repositories

View Markdown

Open Repositories in the local app to browse indexed code and its architectural impact. Use Add repository with a local path, owner/repo, or Git URL.

Indexing extracts files, symbols, and dependencies into a saved snapshot. In Snapshots, choose Take snapshot; enable Include uncommitted changes to capture your working tree. View details shows statistics and indexing warnings.

CLI equivalent: tld index .. See indexing for language tools and setup.

Indexing alone only captures the symbol level code graph. These are usually too fine-grained to be useful for architecture diagrams.

Open a snapshot’s details and choose Map into workspace to group its code graph into nested views. It is driven by graph clustering and community detection algorithms, and can be tuned with Map settings. It’s purpose it to turn the raw code graph indexed to a more digestible , useful components for diagramming.

Open workspace map opens the result in the editor. Mapping preserves existing diagram content and only upserts, tagging old elements stale.

CLI equivalent: tld index . --map.

In Compare, select Base and Head, then click Compare to inspect changed files and their impact on diagrams. Impact radius adds up to two dependency hops around changes; the default is zero.

CLI equivalent: tld git compare HEAD~1 HEAD. Add --mermaid for Mermaid output or --blast-radius 2 for more context. See Git compare for exports and limits.

Use Watch to follow staged, unstaged, and untracked changes against the current commit. Start it from the page or run tld index . --watch.