Smart Connections

Explore related notes from the current note, an exact block, the note footer, or an Obsidian Base. Core and Pro capabilities are documented together, with advanced requirements labeled where they apply.

In this guide

Find related notes in Obsidian with Smart Connections

The Connections view is note-anchored semantic discovery: while Play is active, the current note determines the related notes or blocks shown beside it.

The open note and its ranked Connections list are visible together, showing the current-note anchor without a separate query.

Open the Connections view

Open the Connections view from the Smart Connections ribbon action or Command Palette entry.

The default view uses the active note as the reference source and updates when that source changes while Play is active.

When should I use Smart Lookup instead?

Use Lookup when a question or typed idea should determine the results. Use Connections when the current note is the anchor.

Play and Pause

Play lets the view follow the active note. Pause keeps the current reference note fixed while you open or compare results.

If the list appears stuck after changing notes, confirm that Play is active.

Why did the list change when I opened a result?

The Connections view follows the active note while Play is active. Pause the list before opening results when one reference note must remain fixed.

Drop an item anywhere in Connections to change the target

Drop one indexed note or block anywhere inside the live Connections view, including the top bar, target label, graph, result list, or background.

Accepted sources include a File Navigator note and a Connections, Lookup, or graph result. The view rerenders around the dropped target.

Folders, unindexed items, ambiguous paths, and multi-item drops are rejected because one Connections view has one target.

Refresh

Refresh recomputes results for the current reference note.

Use it after substantial note edits, a settings change, or a stale result state.

Read result rows

Each row represents a related Smart Source or Smart Block.

A row can show:

source or block label
path or heading context
relative connection score
expand/collapse state
pinned or hidden feedback state where applicable

Expand and collapse a result

Expand a result to inspect more source content without opening the note.

Fold/unfold-all controls apply the same presentation state to the visible rows.

Hover preview

On desktop, hold Cmd/Ctrl while hovering a result to use Obsidian Hover Preview.

Preview lets you confirm relevance without changing the active note or the list anchor.

Drag a result into a note or another Smart Plugin

Dragging a verified result turns a recommendation into the next explicit workflow.

Drag a result to:

a Markdown editor to create an Obsidian link
Smart Chat to add it to the current response context
an existing named-context dashboard row to curate it into that saved context
Smart Graph to add its indexed source to the current graph scope
the live Connections view to make it the single current target

Use the editor route when a suggested relationship should become an authored relationship in the current note.

Copy as a list of links

Copy as list of links copies the current result set as Obsidian links.

The output is suitable for a Related section, reading trail, project hub, or review note.

Send to Smart Context

The current result set can become a reviewable Smart Context without rebuilding the source list manually.

Send to Smart Context opens a reviewable context set from the current Connections results.

Remove noisy results before copying or using the set in an AI workflow.

Hide a result

The result menu exposes Hide and Pin beside the other actions available for the current Connections list.

Hide removes a recurring low-value result from the visible list.

Hidden feedback can also affect feedback-aware scoring algorithms when one is selected.

Pin a result

Pin keeps an important result at the front of the list.

Pinned results remain at the front while still showing a score for the current reference note.

Interpret connection scores

The score is a relative ranking signal for the current result list.

Compare scores inside the same list.
Do not treat the score as an absolute grade.
Preview or open the source before using it.
Score ranges vary by model, candidate pool, and algorithm.

Does a high score mean the notes should be linked?

No. It means the result ranked highly for the current comparison. Add a link only after the relationship helps the note.

Choose Sources or Blocks

Smart Sources returns whole-note candidates. Smart Blocks returns heading or block candidates.

Start with Sources for broad discovery. Use Blocks when long notes hide the useful section.

Troubleshoot empty or stale results

Use the smallest recovery that matches the state.

State	First check
Empty on a tiny note	Open a note with enough meaningful text.
Not updating	Confirm Play is active.
Stale after edits	Use Refresh.
Expected note missing	Check Smart Environment exclusions and source eligibility.
Broad or noisy	Tune result type, limits, filters, or scoring only after one useful result is confirmed.

Are similar results duplicates?

Not necessarily. Use Smart Dedupe when repeated material needs side-by-side review.

Connections sidebar behavior

The sidebar owns active-file refresh, pause state, folding, settings access, and visibility recovery.

Auto-open behavior

New installations can open the Connections sidebar automatically so the first result surface is visible.

Existing workspaces retain normal Obsidian view persistence.

Active-file refresh

While Play is active, the sidebar refreshes when the active note changes.

The view also updates after an explicit Refresh action and relevant Connections-list settings changes.

Pause behavior

Pause keeps the current reference source while the active editor changes.

While Pause is active, active-note changes do not refresh the list.

Why are results still anchored to an older note?

Pause may be active. Switch to Play to resume active-note updates.

Settings gear

The gear control opens the relevant Connections settings surface.

Settings changes that affect list filters trigger a result refresh.

Fold or unfold all

Fold/unfold-all changes the expanded state of visible result rows without changing the result set.

Sidebar visibility recovery

When the sidebar is hidden, it defers refresh work. When it becomes visible again, it updates if the active note changed and Pause is not active.

Why did the sidebar not update while it was hidden?

Hidden views defer unnecessary work. The pending source is checked when the view becomes visible again.

Connections mini graph

The mini graph is an alternate display of the current Connections result set, not the full Smart Graph product.

Connections graph

The graph displays the current Connections result set as nodes arranged around temporary semantic groups. Use it to inspect the shape of a result set while the list remains the action-oriented surface.

Node states

Pinned results use the Connections accent treatment. Hidden results remain visible as muted nodes so prior feedback is still recognizable in the graph.

Why can a hidden result still appear?

The graph can keep it as a muted node so prior feedback remains visible.

Graph lines

Lines visualize relationships among the displayed results. They do not create Obsidian links and should be treated as exploratory signals.

Do graph lines create links in my notes?

No. They are visual signals. Add a normal Obsidian link when the relationship should persist.

Preview a node

On desktop, hold Cmd/Ctrl while hovering a node to use Obsidian Hover Preview for the corresponding note or block.

Select a node

Selecting a node scrolls the matching Connections row into view and expands it for review.

Semantic groups

Group placement is recalculated from the current result set. A node can move when the reference note, result set, model, or indexing state changes; the groups are not a durable taxonomy.

Troubleshooting weak or noisy Connections

Open a meaningful note, confirm source import and embeddings, switch from Pause to Play, refresh after major edits, inspect exclusions, and tune Sources, Blocks, filters, Hide, Pin, or Pro algorithms only after the basic view returns a useful result.

Find related notes beside the text you are writing

Inline connections use the current paragraph, heading, or block as the semantic anchor and open a focused result popover in the editor.

Inline indicators appear beside eligible blocks while the whole-note Connections list remains available in the sidebar.

Enable or disable Inline connections

The Inline and Footer settings determine where in-note Connections surfaces appear.

Use the inline-connections command to show or hide inline result markers.

Assign the command to a hotkey when inline results are useful only during review passes.

Understand the inline indicator

A marker appears beside a block when at least one result meets the configured inline threshold.

The marker identifies block-scoped related material; it is not a persisted link.

Why do some paragraphs have no inline marker?

No candidate passed the inline score threshold, the block is excluded, or inline processing is disabled for that content.

Does the marker create a permanent link?

No. Open or drag the useful result into the note when the relationship should become durable.

Open the Inline connections popover

The popover shows the strongest related results for the current block without leaving the editor.

Hover the marker to open the related-result popover for that block.

The popover shows the strongest visible candidates and a path to the full list.

Preview and open a result

Hold Cmd/Ctrl while hovering a result to use Obsidian Hover Preview on desktop.

Open the full result list for a block

Select the popover header that includes the Connections label and line range to open the full result set for that block in the main Connections view.

How do I see more than the popover results?

Open the popover header to send that block anchor to the full Connections view.

Tune the inline score threshold

The inline threshold controls how strong a match must be before a marker appears.

If normal Connections results work but inline markers do not appear, lower the inline threshold before changing indexing or model settings.

Code blocks and unsupported content

Inline processing can skip fenced codeblocks so generated markers do not interfere with code, prompts, or structured block content.

The setting applies only to inline markers; normal Connections results remain available elsewhere.

Inline vs Footer vs the Connections view

Use Inline when one exact block should determine results, Footer for note-end review, and the Connections view for persistent whole-note exploration.

Troubleshooting Inline connections

Lower the threshold when normal Connections works but no indicators appear; raise it when the editor is noisy; confirm the block is eligible; reopen after material edits; treat mobile behavior as release-specific until verified.

Show related notes at the bottom of an Obsidian note

Footer connections mount the Connections result display at the end of the current note and appear when the note ending is visible.

Footer connections appear at the end of the active note, where related results can be reviewed before leaving the page.

Enable Footer connections

Connections settings control whether related results appear inline, in the footer, or both.

Enable Footer connections from Connections settings or an available command/ribbon entry.

Footer uses the same related-result model as the Connections list, mounted at the end of the editor.

When the footer appears

The footer renders only when the end of the note is visible.

This keeps the surface tied to end-of-note review instead of occupying space throughout the document.

Why is the footer not visible?

Confirm Footer connections are enabled and scroll until the last line of the note is visible.

Expand or collapse the footer

Use the footer header to collapse or expand the mounted result surface.

The footer remembers its folded state.

Does collapsing the footer disable Connections?

No. It changes the footer presentation. Re-expand it for the same note-level result surface.

Read and expand footer results

An expanded footer result reveals enough source content to verify relevance before opening the note.

Expand a result to inspect more context before opening the source.

Expansion does not create a link or change the current note.

Drag to create a link

On desktop, drag a result from the footer into the editor to insert an Obsidian link.

Open a result

Open a result when the inline preview is not sufficient.

Use Footer connections on mobile or without a sidebar

The footer keeps related-note review inside the note when a persistent sidebar is inconvenient.

Footer can be more practical than a sidebar on mobile or compact layouts, subject to the current Obsidian and plugin build.

When should I use the sidebar instead?

Use the sidebar for continuous exploration, Pause, copying links, and sending a result set to Smart Context.

Footer vs Inline vs the Connections view

Use Footer for note-end review, Inline connections when one block should determine results, and Smart Connections view for persistent whole-note exploration.

Troubleshooting Footer connections

Confirm the setting is enabled, scroll to the note end, expand the footer, and verify the current note produces normal Connections results.

Tune Smart Connections scoring and ranking

Connections result shaping has three layers: candidate scope, primary scoring, and final ranking.

Score and ranking controls expose the two stages that shape final Connections order.

Choose Sources or Blocks

Select Smart Sources for note-level candidates or Smart Blocks for heading/block-level candidates.

Candidate selection happens before scoring. Fix an overly broad pool before tuning the score.

Configure candidate filters

Include and exclude path filters narrow the candidate pool before scoring and ranking are applied.

Filters decide which candidates are eligible.

Use include/exclude rules for project paths, archives, templates, tags, or other structural boundaries before adding a more complex scoring algorithm.

Choose a score algorithm

Score algorithms compute the primary relevance value.

Algorithm	Use
Cosine Similarity	Stable baseline without feedback.
Similarity Adjusted by Feedback	Penalize candidates similar to hidden results.
Similarity Weighted by Feedback	Boost pinned-like signals and dampen hidden-like signals.
Similarity Weighted by Key + Frontmatter	Apply path, key, heading, or metadata multipliers.

Choose a ranking algorithm

The ranking control separates final-order choices from the primary score algorithm.

Ranking algorithms reorder already-scored candidates.

Algorithm	Use
None	Preserve score order.
Re-ranking model	Apply a configured Smart Rank model to top candidates.
Recency rank	Make modification time dominate final order.

What is the difference between scoring and ranking?

Scoring decides the primary relevance value. Ranking changes the final order after scoring.

Use feedback-aware scoring

Feedback-aware algorithms use pinned and hidden signals.

Use them only when those actions represent stable preference. A one-off hide can otherwise create an unintended recurring bias.

Weight paths, keys, headings, and frontmatter

Weight configuration multiplies the base score when key fragments or metadata match.

{
  "key_weights": {
    "Projects/": 1.2,
    "Readwise/": 0.8
  },
  "meta_weights": {
    "status:evergreen": 1.15,
    "type=spec": 1.1
  }
}

Multiple matches multiply together.

Configure a reranking model

Re-ranking requires a configured Smart Rank model in Smart Environment Pro.

If no compatible ranking model is available, use None or Recency rank.

Rank by recency

Recency rank reorders the scored candidates by modification time.

Use it when freshness should dominate. Do not use it to solve an eligibility or semantic-scope problem.

Troubleshoot broad, weak, or noisy results

Apply tuning in this order:

Fix candidate scope.
Fix filters and limits.
Establish Cosine Similarity as the baseline.
Add score weighting.
Add ranking only when the right candidates remain in the wrong order.

Why did changing three settings at once make results harder to evaluate?

Scope, score, and ranking changed simultaneously. Return to a baseline and alter one layer at a time.

Should I use Dedupe when similar notes keep appearing?

Use Dedupe when repeated material needs a keep, merge, archive, or ignore decision. Use algorithm tuning when the issue is result ordering.

Tune in the correct order

Choose Sources or Blocks, narrow the candidate pool, establish Cosine Similarity as the baseline, change scoring only when relevance is consistently wrong, and add ranking only when the right candidates exist in the wrong order.

Compare algorithm changes

Keep the anchor note, candidate pool, and filters stable while testing one change. Compare useful results across several representative notes rather than comparing score ranges alone.

Rank Obsidian Bases rows by semantic relevance

Connections in Bases compares each represented note with a reference note and exposes the result as formula values that can be sorted or filtered.

A reference note acts as a semantic lens for ranking rows in an Obsidian Base.

Requirements

Use this integration after Smart Connections returns useful results. The active file must be a .base file and Connections Pro must expose the score and link-list functions.

Add a Connections score column

After the score-column action and reference selection, the Base exposes a sortable relevance score beside each row.

Open a .base file and run Add: Connections score bases column.

The command opens a reference-note selector and inserts a formula column that scores each row relative to the selected note.

Why does the score-column command not appear?

The active file must be a .base file and the Pro Bases integration must be available.

Choose a fixed reference note

A fixed reference lens keeps every row comparable against the same note.

Choose a fixed note for a stable comparison or Current/active file (dynamic) for a Base that follows the active note.

Dynamic references work best when the Base is kept in the sidebar.

Why do scores differ from another Base?

Candidate filters, reference note, embedding model, and scoring algorithm can differ. Compare scores only inside the same configured view.

Use the current active note as a dynamic reference

The dynamic option uses the current active file as the comparison target.

Keep the Base visible in a sidebar when it should behave like a filtered, sortable Connections dashboard.

Use `score_connection`

score_connection returns a numeric connection score using the configured Connections scoring algorithm.

score_connection(file, file2)
file.score_connection(file2)

Use `list_connections`

A related-links formula turns each Base row into a direct navigation surface for nearby notes.

list_connections returns a list of related links for a row.

list_connections(file)
file.list_connections()

Use it beside a score column when the Base should show both ranking and an actionable link trail.

Should I use `score_connection` or `list_connections`?

Use the score for sorting and filtering. Use the link list when you also want immediate navigation to related notes.

Bases formula examples

Fixed-reference examples:

file.score_connection("+Projects/Project Alpha.md")
score_connection(file, "+Projects/Project Alpha.md")

Related-link examples:

file.list_connections()
list_connections(file)

Sort and filter by relevance

Filter the Base first to define the candidate set, then sort the score column descending.

A score is most useful as a relative ranking inside one Base and one reference point.

Use a dynamic Base in the sidebar

A Base using the active-file reference can stay docked while you move through notes.

The table then reranks only the rows allowed by the Base filters.

Interpret Connections scores in Bases

Treat the score as a relative signal inside the same Base and reference point. Model, candidate scope, filters, and algorithm choice can change the range.

Troubleshooting Connections in Bases

Confirm a .base file is active, verify source preparation and the reference note, dock dynamic Bases in the sidebar, filter broad collections, and check the configured score algorithm.