Connect Pro FAQs
What is Connect Pro?
#Connect Pro exposes configured Smart Tools from a running Obsidian Desktop vault through Local MCP and Smart CLI Pro. In 2.0, its unified Connect Pro Inbox lets you review AI-proposed corrections and moves before those proposals change source notes. The legacy Remote GPT connection is separately controlled.
Connect Pro is not Sync, a mobile vault, unrestricted shell access, or an autonomous agent. Direct-write Tools outside the dedicated proposal workflow are not automatically held for review.
What changes in Connect Pro 2.0?
#The central workflow is propose, review, then apply or reject. Three Tools cover exact corrections, excerpt moves with optional rewritten insertion, and complete block moves. The Inbox adds editable previews, destination and block-order controls, Pending and History views, Group and Label filters, and priority-based review order.
get_proposal_feedback exposes saved proposals and decisions as historical evidence. Local MCP and Smart CLI use the same Smart Tool contracts, with separate connector availability controls. Source checks, checked writes, and conservative recovery protect the application path without promising Undo or crash-atomic transactions.
Does Connect Pro require anything extra?
#Keep the intended vault open in Obsidian Desktop 1.12.2 or later with Connect Pro 2.0 enabled and its required Pro access active. For Local MCP, start Local MCP server and connect a trusted supported client on the same computer using Set up desktop clients.
Enable Obsidian CLI for Smart CLI and native CLI operations; it is not a blanket prerequisite for every Local MCP Smart Tool. An Active plugin row does not prove that a connector or client is ready. Read one recognizable note before proposing a change.
Does Local MCP require Remote GPT to be connected?
#No. Local MCP has its own Running state and endpoint. Remote GPT can remain Disconnected while a local client uses enabled Tools. Disconnecting Remote GPT does not stop Local MCP, and stopping Local MCP does not disconnect Remote GPT or disable Smart CLI.
A running listener is not proof of client discovery or a successful read from the intended vault. Check those separately.
Local MCP is Running while Remote GPT is Disconnected. Use the endpoint shown in your own installation; a running listener does not establish client discovery or a successful vault read.
What actions can Connect Pro run?
#Use the current client's Tool list and Connect Pro settings > Tool permissions > Tool actions. Installed capabilities can supply retrieval, exact reads, Context workflows, native CLI operations, direct writes, and explicit reviewable proposals. Availability depends on installed plugins, the current host session, and per-channel controls.
The proposal Tools are propose_correction, propose_move_excerpt, and propose_move_blocks. The read-only feedback Tool is get_proposal_feedback.
Do the individual CLI controls restrict every CLI route?
#No. Obsidian CLI and Local MCP are separate availability controls for listed Smart Tools. Individual Obsidian CLI tools controls the native commands exposed as individual Local MCP Tools.
The broad Obsidian CLI action, obsidian_cli, is not restricted by those individual command settings. Disable it as well when you need that narrower boundary. These controls do not restrict unrelated registered Obsidian CLI commands, and new Smart Tool actions default to enabled.
An enabled control does not prove discovery or execution. A disabled Smart CLI action is blocked immediately, although it can remain listed until Obsidian restarts.
Each proposal Tool has separate Obsidian CLI and Local MCP controls. Enabled rows show availability, not invocation or a complete read-only boundary. The broad obsidian_cli action is outside this crop.
Does Connect Pro ask before every action?
#No. Client confirmations belong to the client, and Tool effect annotations describe effects rather than create an approval boundary. Unrelated direct-write and native CLI actions are not held in the Inbox.
propose_correction, propose_move_excerpt, and propose_move_blocks save pending proposals without changing source files. Their source changes happen only when you apply the reviewed proposal in Obsidian.
Why did a proposal succeed without changing my note?
#That is expected. The result includes status: pending, source_files_changed: false, and the saved item key. Open the ribbon action Open Connect Pro Inbox, the Command Palette action Open: Connect Pro Inbox view, or settings > Review and activity > Connect Pro Inbox.
A new destination note is created only when the proposal is applied. Pending review is a successful proposal outcome, not a missing write to retry.
Which proposal Tool should I use?
#Use propose_correction for one exact claim supported by an exact reference excerpt. Use one independent phrase, sentence, list item, or table cell per call. The target excerpt must occur exactly once within the selected target. Supporting evidence still needs human evaluation.
Use propose_move_excerpt for one exact passage that should move, optionally with different insertion wording. Use propose_move_blocks for complete discovered blocks and their children, in the desired final order. Block moves do not synthesize content, rewrite headings, delete source notes, or repair links.
Use returned source and block keys rather than constructing them. Overlapping parent and child selections are not valid block-move inputs.
Can I correct a proposal before applying it?
#Yes. Corrections and excerpt moves offer Changes, Before, and After views. A new destination has no Before view because the file does not exist yet. Edit the permitted replacement or insertion in the review, select another destination with Change, or reorder the originally selected blocks.
Done editing retains a local draft without applying or saving a final decision. Cancel restores the text from the start of the editing session. Relevant edits require a fresh preview. Adding or removing selected blocks requires a new proposal.
*Done editing keeps the proposed replacement as a review draft; it does not apply the correction. Check the evidence and refreshed diff before using the separate Apply correction action.*
Why does a move need two confirmations?
#An excerpt that is both moved and rewritten requires separate approval of the original removal and the rewritten insertion. Both must be satisfied before Move and rewrite is available. A relevant edit resets them.
An unchanged excerpt move uses Move excerpt. Plain block moves preserve selected text and heading levels; they do not silently turn moved headings into subsections of the destination.
Both confirmations are unchecked, so Move and rewrite is disabled. Review the rewritten insertion and exact original removal separately. Link impact not checked remains an explicit limit.
Can a move create a new note?
#Yes, with an explicit new-note destination. The Tool uses destination_mode: create with a new vault-relative .md or .txt path. In the Inbox, use Change > Create new note.... Creation happens only on application.
destination_mode: append requires an existing note or block. Missing append targets and missing sections are not created automatically. When a new-note path becomes occupied during review, select the intended mode and destination and inspect a fresh preview.
Does repeating a proposal create duplicates?
#An identical still-valid pending proposal returns the existing key with deduplicated: true. This is exact pending deduplication, not semantic similarity detection. Changing only the reason, priority, group, or label does not silently modify the existing item. Rejection does not permanently suppress future proposals.
A proposal already being reviewed or requiring manual recovery is not a safe retry target. Inspect its status instead of repeatedly submitting it.
What do Group, Label, priority, and History mean?
#Group identifies a project or review batch. Label identifies a reusable category. Their filters help locate independent proposals; neither creates a shared approval.
Priority controls pending review order: high before normal before low, then oldest first. It is not confidence or permission. Skip leaves an item pending. History contains applied and rejected decisions, most recently reviewed first.
This captured session ends with two Applied moves and one Rejected correction. History records those decisions; inspect the actual notes for their resulting contents. It is not Undo.
Can agents use my previous review decisions?
#Yes, through get_proposal_feedback when it is available and enabled. It can retrieve an exact item key or filtered lists of saved proposals and decisions. Lists default to reviewed items and 10 results; the page limit is 1 through 25. Pass an exact key alone, or pass a returned next_cursor as cursor alone to continue the same list query.
For applied items, comparison: edited includes original proposed and final applied values. unchanged establishes that those values matched. unknown means original comparison evidence is unavailable. Do not infer unchanged from missing proposed values.
Does proposal feedback automatically learn my preferences?
#No. It returns historical decision evidence, not a preference model. A rejected item means the whole proposal was declined, not that a particular field or rationale was rejected. proposal_reason is the proposer's rationale, not a human rejection reason. A pending item contains no human decision.
Repeated keys, similar batches, recent decisions, partial pages, or an empty result do not establish a global rule. Historical context is not current-source truth or authorization to apply. Agents should ground observations in item keys, follow current instructions, and read current notes separately before proposing another change.
What does Manual recovery required mean?
#An application attempt left file changes or the saved review decision unresolved. Inspect the named files and saved review state before proposing another change. The affected item remains blocked from application; inspection alone does not reset it.
Recovery attempts are conservative and do not promise to restore every file. In particular, a new destination can be retained for manual inspection. Rejecting the item does not restore partially recovered content or resolve the recovery requirement.
Can I undo an applied proposal?
#The Inbox has no user Undo command or automatic link repair. It attempts recovery for application failures, but that is not a crash-atomic multi-file transaction. Keep a suitable backup or version-history workflow.
History records applied and rejected outcomes; it is not an Undo mechanism. Inspect the resulting notes. If a change is applied but source indexing needs a refresh, refresh indexing rather than applying it again.
Is Tool action requests the same as Inbox History?
#No. Review and activity > Tool action requests > View requests shows completed request payloads retained for the current Obsidian session. It helps inspect a specific invocation. History is the saved record of applied and rejected Inbox proposals. Neither a completed request nor a pending proposal proves that a source change was applied.
Where did my old contradiction or move queue go?
#The unified Inbox loads its native inbox_items store. It does not import or modify the earlier separate contradiction, Extract, or Merge stores. Native items already present remain; removing migration does not undo an earlier import.
Refresh client discovery and use propose_correction, propose_move_excerpt, and propose_move_blocks. Earlier experimental Tool names and queue labels are historical, not the v2 public contract.
Is my vault content guaranteed to stay on this device?
#No. Local MCP describes the listener's location. A connected client can send Tool inputs and returned vault content to its model provider. Connect clients you trust and expose only the capabilities needed for the current workflow.
Can I use the Official Connect Pro GPT from any device?
#This is a separate legacy route, not a Local MCP feature. It requires an available supported GPT integration, a connected Remote GPT session, and the running desktop vault. Local MCP readiness alone does not establish remote or cross-device support.
Is Connect Pro the same as Smart Chat?
#No. Smart Chat owns its in-Obsidian conversation experience. Connect Pro exposes bounded vault capabilities to an external calling client. The Inbox owns human review of the dedicated correction and move proposals, not every Smart Chat or vault operation.
Does installing Connect Pro migrate an older Smart Connect or Custom GPT Actions setup?
#No automatic connection migration is established by the v2 Inbox work. Make sure that a replacement route works before dismantling a working legacy connection. Connection migration and old Inbox-record migration are different concerns.
Does this canon define a separate public API or OpenAPI workflow?
#Local MCP is an implemented local connector, and Smart CLI is a registered command surface. Neither establishes a public hosted MCP endpoint or a separate public OpenAPI setup. A loopback listener is not publicly reachable merely because it is Running.
Where is the Smart Connect app?
#Connect Pro is the current plugin direction in this project. Older Smart Connect material is historical setup context. Use the installed instructions and check the replacement route rather than assuming compatibility.