Links, backlinks, and graph

Wikilinks

Link one doc to another with a wikilink: [[name]]. In Preview and Split modes the link is clickable and jumps to the target. Type [[ in Source mode to trigger autocomplete — a dropdown suggests matching docs in your workspace.

A wikilink resolves to a doc by, in order:

1. Filename without extension: [[architecture]] → architecture.md
2. Relative path without extension: [[adr/0001-choice]] → adr/0001-choice.md
3. Frontmatter title: [[Backend Architecture]] resolves a doc whose title: matches

Matching is case-insensitive and the .md extension is optional: [[CLAUDE]], [[claude]], and [[claude.md]] all resolve to CLAUDE.md.

Example — linking between docs:

We follow the constraints in [[CLAUDE]] and the decisions in [[adr/0003-api-versioning]].
The detailed system diagram is in [[arch/overview]].

Backlinks

The Backlinks tab in the Inspector (right panel, ⌘**) shows every doc that contains a wikilink to** the currently open doc, with the line where the link appears. Click a backlink to open that doc.

Direction note: backlinks are incoming. If doc A contains [[B]], that link appears in B’s backlinks — not in A’s. So the links you write in a file appear on the target’s backlinks list.

Example: you’re reading architecture.md. The Backlinks tab shows: - plans/v2.md, line 12: See [[architecture]] for background. - adr/0009-caching.md, line 4: This builds on [[architecture#caching]].

Click either entry to open that doc.

Graph view

Open the graph with the network icon in the top bar, or via the command palette (⌘K → “Open graph view”). It shows all your docs and prompts as nodes connected by wikilinks:

• Click a node to open that doc in the editor.
• Drag nodes to rearrange the layout.
• Zoom with scroll or pinch.
• Dense clusters — tightly connected areas of related material.
• Isolated nodes — orphan docs with no incoming or outgoing links.

Flow document

From the graph view or the command palette (⌘K → “Generate flow document”), Bedrock regenerates Flow.md — an auto-built map of the whole workspace listing all docs by type and all prompts by category, with their connections.

Use Flow.md as a navigation aid for an AI: give it to the model alongside your context docs so it knows where everything is in the workspace.