Connect Pro for Obsidian

Use to find semantically related notes or blocks anchored to one known Smart Source. Returns one ranked connection list for the exact source key, with optional result content. Pinned or hidden rows include target-local feedback; omitted feedback means no recorded feedback for that target. Feedback is not a global preference, confidence, or access rule. Hidden and pinned rows retain their ranked slots within limit; pins outside that window are not appended. Do not use for free-form search or per-block analysis; use smart_lookup_query for a query and smart_connections_pro when each embedded block needs a separate connection list.

smart_connections_list

Use for granular, per-block semantic analysis of one known Smart Source. Returns ranked connections for each embedded block, always includes the source content, and can include connected-item content. Pinned or hidden connections include feedback for their specific target block; omitted feedback means no recorded feedback for that block. Feedback is not a parent-source or global preference, confidence, or authorization. Hidden and pinned rows retain ranked slots within each block limit; pins outside that window are not appended. Do not use when one source-level ranked list is sufficient; use smart_connections_list instead.

smart_connections_pro

Use to discover existing named Smart Contexts or resolve an uncertain context name from their names, keys, and descriptions. Do not use when an exact name or key is already known, or to read context items or content; use smart_context_get. This tool does not modify contexts.

smart_context_list

Preview one pending Inbox proposal using stored values, not unsaved UI drafts. Returns its reason and either guarded file dependencies with explicit create/modify/delete operations and separate advisory reference status or one captured native CLI invocation, without changing the proposal or executing it. Whole-file merges refresh their complete source evidence while preserving rewritten insertions; ordinary excerpt/block selections stay fixed. Confirmed source-deleting merges attempt native link updates using Obsidian; this preview does not update links. Reference-only changes do not block inspection or approval. Fails for affected sources that change during preview, unconfirmed saves, active reviews, or recovery blocks. Truncated output is incomplete and must not be treated as fully inspected. A successful preview is informational, not approval or an Apply token.

preview_proposal

Use after verifying that one exact target excerpt conflicts with an exact reference excerpt and a concrete replacement or deletion can be proposed. Omit replacement_excerpt or pass an empty string for deletion. Queues one atomic pending Inbox correction and does not edit either source. Successful results contain key, status=pending, deduplicated, and source_files_changed=false. Applying the correction is a separate user action in Obsidian. Reference changes after creation produce advisory warnings, not Apply blockers; affected files must still match the reviewed plan. Identical valid pending corrections are reused. Use one call per independent phrase, sentence, list item, or table cell; additional_evidence is only for concise support that is not an exact reference excerpt.

propose_correction

Queue one coherent pending Inbox edit set for human review without modifying source files. Supports exact replace/remove, positioned insertion, and explicit creation, including forks, split notes, synchronized summaries, and synthesis. All targets and anchors refer to original snapshots, not intermediate results. Supply only fields belonging to each operation: replace requires target_excerpt and replacement_text; insert requires position and insert_text, plus anchor_excerpt only for before/after; create requires content. Text and whitespace are literal. Declare every source used to derive text in read_dependencies, even when it remains unchanged. Only a comparable source/block hash difference produces a change warning; pending imports and missing metadata remain neutral; review does not reread reference files. Changed, stale, missing, or unavailable reference data does not block review or Apply; affected file snapshots still must match the reviewed plan. Review can edit final text, not targets or evidence. One approval covers every file. Recovery is not a crash-atomic transaction: uncertain recovery, newly created outputs, or interdependent preservation cycles may require manual inspection before retrying. No file deletion, renaming, link repair, or native command execution. Prefer the existing specialized proposals where suitable. Identical valid pending edit sets are reused; success returns status=pending and source_files_changed=false. Application is a separate user action in Obsidian.

propose_edit_set

Queues one or more unchanged blocks in exact array order for human review in the Connect Pro Inbox. This is a move, not copying, synthesis, or note merging: unselected text and original notes remain, and moved headings/links are not rewritten. Optional source_replacements leave exact continuity text in place of selected blocks. This call saves review data without editing source files. Successful results contain key, status=pending, deduplicated, and source_files_changed=false. Applying the move is a separate user action in Obsidian. Optional placement selects append (default) or prepend; line_anchor_text selects a unique exact full destination line. Without an anchor, placement uses the target end/start and preserves whole-note frontmatter. Invalid placement or missing/ambiguous anchors fail without fallback. Identical valid pending proposals are reused.

propose_move_blocks

Queues an exact excerpt move, not a copy, or a whole-file merge for human review in the Connect Pro Inbox. This call saves review data without editing source files. Successful results contain key, status=pending, deduplicated, and source_files_changed=false. Optional insert_text changes only the proposed insertion; source_replacement specifies text left at the source. Applying the proposal is a separate user action in Obsidian. Ordinary moves retain source files and do not retarget whole-note links. With delete_source_file=true, confirmed application verifies the destination before moving the original to trash and invoking native link handling under Obsidian preferences. Optional placement selects append (default) or prepend; line_anchor_text selects a unique exact full destination line. Without an anchor, placement uses the target end/start and preserves whole-note frontmatter. Invalid placement or missing/ambiguous anchors fail without fallback. Identical valid pending proposals are reused.

propose_move_excerpt

Query-purpose semantic retrieval only. No hypothetical document or chat model is used.

smart_lookup_query

Use to read the text of one existing Smart Block when its exact block key is known. Do not use for an entire source or discovery; use smart_source_read for a source and smart_lookup_query with results_collection_key set to smart_blocks when the key is unknown. This tool does not modify the vault.

smart_block_read

Use to read the full text or metadata of one existing Smart Source when its exact key is known. Do not use for a block key or discovery; use smart_block_read for a block and smart_lookup_query when the key is unknown. This tool does not modify the vault.

smart_source_read

Use to remove one source, block, vault-relative path, or external path from an existing named Smart Context. Prefer an exact item key returned by smart_context_get; repeated removals are safe and the context itself is not deleted. Do not use to delete or clear the entire context.

smart_context_remove

Use for semantic discovery when the request is expressed as a topic, question, or concept and no exact source or block key is known. Accepts query, hypothetical_document, or both. If document retrieval fails after query retrieval succeeds, query-only results are returned. Returns ranked keys, scores, and optional content without calling a chat model. Do not use to read a known key or find items related to a known source; use smart_source_read, smart_block_read, or smart_connections_list.

smart_lookup

Use only to set or clear the plain-text description of an existing named Smart Context. It does not rename the context or change its items; use smart_context_add or smart_context_remove for membership changes. An empty description clears it.

smart_context_update

Use to append text to the end of an existing vault file without replacing its current content. Provide content and normally an explicit path or unambiguous file name; rely on the active file only when the request explicitly refers to it. Do not use for structured +Outcome notes, prepending, or whole-file replacement. With Connect CLI write review enabled, this write is queued in Smart Inbox before execution. Exact path/content/inline requests receive a file-change preview; other supported arguments are shown as a captured native call.

Use to list existing Obsidian bookmarks, optionally returning only a count, including bookmark types, or selecting a structured output format. This is read-only and does not create or modify bookmarks. Do not use for links, recently opened files, or content search.

Use to list vault files that contain no outgoing internal links. This is read-only and differs from orphans, which lists files with no incoming links. Request total only when the count alone is needed.

Use to list vault files that have no incoming internal links from other files. This is read-only and differs from deadends, which lists files with no outgoing links. Request total only when the count alone is needed.

Use to insert text at the beginning of an existing vault file after any frontmatter while preserving the rest of the file. Provide content and normally an explicit path or unambiguous file name; rely on the active file only when explicitly requested. Use append to add text at the end.

Use to read one named property value from a specific vault file. Provide the exact property name and normally an explicit path or unambiguous file name; use the active file only when explicitly requested. Do not use to read the full note or all source metadata; use smart_source_read when an exact Smart Source key is known.

property_read

Use to set one frontmatter property on a specific vault file, including an explicit property type when needed. This modifies the file, so provide the exact property name, value, and normally an explicit path or unambiguous file name; use the active file only when explicitly requested. Do not use to remove a property.

property_set

Use to list files recently opened in Obsidian, or return only their count. This is read-only and reflects open-history recency, not recently modified files or semantic relevance. Do not use as a substitute for search.

Use for lexical vault search when matching lines and file paths are needed, especially for exact words, phrases, identifiers, or syntax. Returns grep-style path, line, and text context and can be folder-scoped or case-sensitive. Do not use for semantic or conceptual retrieval; use smart_lookup_query.

search_context

Use to inspect one task or change its status when its exact file and line, reference, or daily-note line is known. Use tasks first when the task location is unknown. This tool modifies the note when toggle, done, todo, or status is supplied; omit update fields for read-only inspection.

Use to discover and list tasks across the vault or within a specific file, the active file, or today's daily note, with optional completion or status filters and line references. This is read-only. Use task only after selecting a specific task that must be inspected or updated.