Smart Connections

Find related notes from the current note, an exact block, the note footer, or an Obsidian Base. The Connections view and Footer connections are included in Core and remain available when Pro is active. Inline connections and Connections in Bases require Pro.

In this guide

• Find related notes in Obsidian with Smart Connections (Core and Pro)
• Find related notes beside the text you are writing (Pro)
• Show related notes at the bottom of an Obsidian note (Core and Pro)
• Tune Smart Connections scoring and ranking (Pro)
• Rank Obsidian Bases rows by semantic relevance (Pro)

Find related notes in Obsidian with Smart Connections

Edition: Core and Pro.

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

The ranked list is the primary workflow. The mini graph appears when the Pro Version 4.0 (Graph + List) component is selected.

What the numbers identify:

1. The note in the editor supplies the current comparison text.
2. The panel header names the Connections target.
3. The mini graph shows the current candidate neighborhood.
4. Ranked rows preserve readable source identities and relative scores.

Use the populated list to choose a result to inspect. Scores are relative signals, and the mini-graph lines are not authored links.

Open the Connections view

Open the Command Palette. Run the command for your installed edition:

• Core: Smart Connections: Open: Connections view
• Pro: Smart Connections Pro: Open: Connections view

What the numbers identify:

1. The full Pro command in the Command Palette search field.
2. The matching Open: Connections view command ready to run.

Core uses the same command suffix under the Smart Connections prefix.

The Smart Connections ribbon action opens the same Connections view when that entry is available. Run the command or select the ribbon action. Wait for the populated Connections view.

The default view uses the active note as the reference source and updates when that source changes while auto-refresh is running.

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.

Auto-refresh and fixed-target behavior

When the active-state menu offers Pause auto-refresh, active-note changes drive the result set. Select Pause auto-refresh when one reference note must remain fixed while you open or compare results.

If the list appears stuck after changing notes, examine the auto-refresh menu state. If auto-refresh is paused, use the available resume action.

What the numbers identify:

1. Beta Reader Feedback is open in the editor.
2. Landing Page Messaging remains the fixed Connections target.
3. The play control resumes auto-refresh.
4. The ranked result set remains attached to the fixed target.

The target stays fixed while another note is open. Resume auto-refresh when you want results to follow the active note again.

Why did the list change when I opened a result?

The Connections view follows the active note while auto-refresh is running. Select Pause auto-refresh 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. Valid drop areas include the top bar, target label, graph, result list, and background.

The target menu groups recently used notes under History and heading or line-range targets under Blocks. Changing the target does not change whether result rows use Sources or Blocks.

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 connections

Refresh connections recomputes results for the current reference note.

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

What the numbers identify:

1. Pause auto-refresh keeps the current target fixed while you inspect another source.
2. Copy as list of links copies the visible result set.
3. Open random connection opens one candidate for review.
4. Scoring algorithm opens the Pro primary-score selector. Ranking and settings remain visible below it.

Review the visible result set. Make sure that the destination is correct. Then choose an action.

Send to Smart Context requires Smart Context. Explore in Smart Graph requires Smart Graph. Scoring and ranking controls require Connections Pro. Check the Store when a handoff is unavailable.

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

What the numbers identify:

1. The panel target is Landing Page Messaging.
2. The mini graph visualizes the current candidate set.
3. The expanded row keeps its source identity and relative score.
4. The expanded Markdown exposes source text for review.

The score is relative to this result set. Expand the row to inspect the source before deciding whether to use it.

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

Drag a result to:

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

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

The preview supports the decision. The inserted Obsidian link makes the reviewed relationship durable.

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

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.

This action requires Smart Context. If Context is unavailable:

1. Open the Smart Plugins Store.
2. Install Smart Context if it is not installed.
3. Enable Smart Context if it is disabled.
4. If the Store shows Reload required, complete that action.
5. Return to Connections.

What the numbers identify:

1. Undo reverses the handoff before you copy or send the reviewed set onward.
2. The summary reports 15 sources, the estimated token size, and one rule.
3. The expanded Newsletter Launch tree preserves the transferred source hierarchy and names.
4. Copy context is available after review.

Sending results creates a reviewable source set. Confirm the identities before copying or sending it onward.

Hide a result

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

In Connections Pro, 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 whole-note Sources or smaller 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.

Hide notes already linked from the current note

Edition: Pro.

Use Exclude outlinks when the current note already links to sources that should not be suggested again. This setting filters the displayed Connections list. It does not delete links, remove notes from the vault, or change Smart Environment indexing scope.

Workflow:

• Start from a note that links to one or more current Connections results.
• Open Connections Pro settings.
• Enable Exclude outlinks.

What the numbers identify:

1. The description limits Exclude outlinks to displayed Connections results. It does not change Smart Environment indexing.
2. The enabled toggle applies that display filter to the current anchor.

After enabling it:

1. Return to the same anchor.
2. Make sure that linked notes are absent.
3. Make sure that unrelated results remain.

Disable Exclude outlinks when you want linked notes to be eligible again.

See the filter explanation for the control and comparison steps.

Troubleshoot empty or stale results

Use the smallest recovery that matches the state.

What the numbers identify:

1. Total indexed items.
2. Remaining and unexpected embedding work.
3. Smart Sources eligibility and current coverage.
4. Smart Blocks eligibility and current coverage.

Coverage shows preparation status. Relevance still depends on the active note and Connections settings.

Inspect one active note with Source Inspector

When one meaningful note is unexpectedly missing:

1. Keep that note active.
2. Choose Inspect active note from the Smart Environment status menu.
3. In Source Inspector, make sure that the note is eligible.
4. Make sure that its required Smart Source or Smart Block state is current.
5. Correct its inclusion or content before you change Connections Pro ranking controls.

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 results are visible.

Existing workspaces retain normal Obsidian view persistence.

Active-file refresh

While auto-refresh is running, the sidebar refreshes when the active note changes.

The view also updates after Refresh connections and relevant Connections-list settings changes.

Fixed-target behavior

Pause auto-refresh keeps the current reference source while the active editor changes.

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

Why are results still anchored to an older note?

Auto-refresh may be paused. Turn it back on from the same control to resume active-note updates.

Settings gear

The gear control opens the relevant Connections settings.

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 auto-refresh is running.

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.

In Pro, the main Connections list can use Version 4.0 (Graph + List) while Footer can use List only. Graph visibility follows the selected component. There is no separate Show graph setting.

Use the mini graph to scan the result set. Then use the list to open a source. Review the source before you keep the relationship.

Connections graph

The graph displays the current Connections result set as nodes arranged around temporary semantic groups. Use it to examine the shape of the results. Then use the list to review a source. Act on the source only after this review.

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

1. Open a meaningful note.
2. Make sure that source import and embeddings are current.
3. Leave auto-refresh running.
4. After major edits, use Refresh connections.
5. Examine the exclusions.
6. 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

Edition: Pro.

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

What the numbers identify:

1. The purple marker belongs to the nearby editor passage.
2. Lines 3-11 names the block range used as the anchor.
3. Each row names a candidate source.
4. The displayed values are relative connection scores.

The marker and popover are temporary discovery controls, not persisted links.

Enable or disable Inline connections

Run Smart Connections Pro: Toggle: Inline connections to show or hide inline result markers.

Assign the command to a hotkey when Inline connections 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

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. The Connections view opens the full result set for that block.

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. Change indexing or model settings only if markers still do not appear.

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 the surfaces as follows:

• Use Inline when one exact block is the intended target.
• Use Footer for note-end review.
• Use the Connections view for persistent whole-note exploration.

What the numbers identify:

1. Show inline connections enables paragraph-level markers.
2. The inline threshold controls when a marker appears.
3. Skip code blocks controls whether code content receives markers.
4. Footer connections list component chooses the note-end renderer. The enable toggle is visible above it.

Troubleshooting Inline connections

• If normal Connections works but no indicators appear, lower the threshold.
• If the editor is noisy, raise the threshold.
• Make sure that the block is eligible.
• Reopen the Inline connections popover after material edits.

Show related notes at the bottom of an Obsidian note

Edition: Core and Pro.

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

What the numbers identify:

1. The note content ends before the Footer surface begins.
2. Smart Connections identifies the Footer result surface.
3. The expanded row keeps its source identity and score.
4. The preview exposes source content without changing the note.

Use the footer to inspect note-end results. Expand a result when you need more source content. Placement and gestures can vary on mobile.

Enable Footer connections

Run Smart Connections: Toggle: Footer connections, or enable Footer connections in Connections settings.

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

Choose the Footer list component

Footer connections list component controls only the result component mounted at the bottom of notes.

• List only keeps the note ending compact and puts the result rows first.
• Version 4.0 (Graph + List) adds the Connections mini graph above the same result list. Use it when the visual overview is worth the additional vertical space and rendering work.

This setting is independent from the main Connections List Component setting and does not change Connections codeblocks.

There is no separate Show graph setting. Select List only to omit the graph or Version 4.0 (Graph + List) to include it.

Why is there no graph in the footer?

The Footer has no graph when Footer connections list component is set to List only. Select Version 4.0 (Graph + List) when you want the mini graph.

When the footer appears

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

This keeps Footer connections at the end of the note 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 results.

The footer remembers its folded state.

Does collapsing the footer disable Connections?

No. It changes only the footer presentation. Re-expand it to see the same note-level results.

Read and expand Footer connections results

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

Footer connections provide a note-end surface when a sidebar is impractical. On mobile, use the controls available in your installation.

Use List only to keep the Footer compact. Choose Version 4.0 (Graph + List) only when the additional overview is worth the extra space.

If Smart Environment loading is deferred:

1. Select Load Smart Environment.
2. Wait for Smart Environment ready or Ready.
3. Then diagnose the Footer.

When should I use the sidebar instead?

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

Footer vs Inline vs the Connections view

Use the surfaces as follows:

• Use Footer for note-end review.
• Use Inline connections when one block is the intended target.
• Use the Smart Connections view for persistent whole-note exploration.

Troubleshooting Footer connections

1. Make sure that the setting is enabled.
2. Scroll to the end of the note.
3. Expand the Footer.
4. Make sure that the current note produces normal Connections results.

If the Footer is too large, set Footer connections list component to List only. If you want the mini graph, select Version 4.0 (Graph + List).

Tune Smart Connections scoring and ranking

Edition: Pro.

These Connections Pro controls shape results in three layers: candidate scope, primary scoring, and final ranking.

Set the candidate type before scoring

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.

What the numbers identify:

1. Connection results type chooses Sources or Blocks.
2. Results limit bounds the visible candidate count.
3. Sidebar location controls where the persistent view opens.
4. Connections List Component chooses the current renderer.

Candidate type and limit shape the pool before scoring or ranking.

Configure candidate filters

Filters decide which candidates are eligible.

Use include and exclude rules to set structural boundaries. Examples include project paths, archives, templates, and tags. Apply these rules before you add a more complex scoring algorithm.

What the numbers identify:

1. The filter notes distinguish display filtering from Smart Environment ingestion.
2. Exclude inlinks removes notes that already link to the target from displayed results.
3. Exclude outlinks removes notes already linked from the target from displayed results.
4. The Include filter restricts displayed results to paths containing Newsletter Launch.

Connections filters change the visible candidate set. They do not delete notes or change which sources Smart Environment indexes.

Choose a score algorithm

Score algorithms compute the primary relevance value.

What the numbers identify:

1. The scoring selector controls the primary relevance calculation.
2. Cosine Similarity is selected.
3. The menu lists the current feedback and key/frontmatter alternatives.
4. Ranking remains a separate step below scoring.

Choose one algorithm. Refresh the same target. Compare the results. Keep the change only when the results improve consistently.

Choose a ranking algorithm

Ranking algorithms reorder already-scored candidates.

What the numbers identify:

1. Scoring remains Cosine Similarity.
2. The separate Ranking algorithm control changes final order.
3. None preserves score order.
4. Re-ranking model and Recency rank are the other visible choices.

Select a ranking method. Refresh the same target. Compare the results. Keep the change only when the results improve.

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:

1. Fix candidate scope.
2. Fix filters and limits.
3. Establish Cosine Similarity as the baseline.
4. Add score weighting.
5. 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

1. Choose Sources or Blocks.
2. Narrow the candidate pool.
3. Establish Cosine Similarity as the baseline.
4. Change scoring only when relevance is consistently wrong.
5. Add ranking only when the correct candidates are in the wrong order.

Compare algorithm changes

Keep the target, candidate pool, and filters stable. Test one change. Compare useful results across several representative notes. Do not compare score ranges alone.

Do not judge an algorithm from its settings alone. Compare result sets while keeping the target, scope, filters, and candidate pool fixed.

Rank Obsidian Bases rows by semantic relevance

Edition: Pro.

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

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

1. Open a .base file.
2. Run Smart Connections Pro: 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.

What the numbers identify:

1. A .base file with five reviewed source rows is active.
2. The full Add: Connections score bases column command is entered.
3. The matching command is ready to run.

Run the command while the intended Base is active. Make sure that the new score column appears. Then configure its reference.

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

Choose one reference:

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

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

What the numbers identify:

1. The same five-row Base remains visible behind the selector.
2. The requested reference path is visible in the selector.
3. Landing Page Messaging.md is the fixed note ready to choose.

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.

What the numbers identify:

1. The .base file remains the destination for the generated column.
2. The selector is filtered to the active-file option.
3. Current/active file (dynamic) is ready to choose.

Choose a dynamic reference. Change the active note. Make sure that the scores update as expected.

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

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.

What the numbers identify:

1. The Base still contains the same five reviewed rows.
2. The Relevance formula column contains Connections values.
3. The fixed reference note scores 1 against itself.
4. The remaining values are ordered from highest to lowest.

Compare values only inside this Base and reference configuration.

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

1. Make sure that a .base file is active.
2. Check source preparation.
3. Check the reference note.
4. Dock dynamic Bases in the sidebar.
5. Filter broad collections.
6. Check the configured score algorithm.

Related documentation

• Search by a typed question
• Review repeated content
• Copy a Base as AI context