Connect Pro FAQs

Read the error beside Desktop apps (Local MCP). For a reported port conflict, resolve the competing listener and select Retry, or choose an available port in Desktop apps (Local MCP) > Setup > Local MCP port. Changing tool permissions will not fix a server-start error. Keep the vault open and use Copy diagnostics when the error persists.

Yes. Desktop apps (Local MCP) > Setup > Local MCP port accepts an integer from 1024 to 65535. Apply saves it and restarts Local MCP if enabled. Update existing desktop-app configurations to the new Server URL afterward; their saved URLs do not change automatically. Leave a working port unchanged unless you need a different one.

For Desktop apps (Local MCP), check that the status says Running on this computer. Compare the app's URL with the current Server URL in this vault, then refresh the app's server or tool list. Follow your client's setup section, including the generated extension for Claude. An old port, a configuration copied from another vault, or a remote/cloud connector pointed at 127.0.0.1 can prevent access. Do not expose the local listener publicly to work around this.

For the ChatGPT plugin (Remote MCP), keep the intended desktop vault open, connect its shared Connect session, and enable ChatGPT plugin. Waiting for Connect means that remote prerequisite is missing; Local MCP running does not establish Remote MCP readiness. If the shared session is Connected but Remote MCP is not Ready, inspect its displayed failure stage/code and use Retry when offered. Rejected desktop authorization requires signing in again through Pro plugins. Service-unavailable or protocol-mismatch messages require checking the paired service with support; changing the Local MCP port does not address those remote failures. A session-replaced message means another desktop owns the active session, so reconnect here only when this is the intended vault.

Stop using that connection. In the intended vault, select Setup beside Desktop apps (Local MCP) and compare its suggested name and URL with the app's configuration. For the ChatGPT plugin or legacy GPT, check Connect session in the intended running vault. Reconfigure the intended connection, then read a recognizable note before making changes.

Check its plugin, the relevant switch in Tools > Manage tools, and the app's refreshed tool list. Native CLI operations also require Obsidian CLI support. Semantic lookup needs its configured index/provider to be ready; a working connection does not establish that.

For an unavailable read, confirm the exact note path or returned source key. Do not broaden access or substitute another vault merely to make the request succeed. See the examples' requirements.

Connect Pro lets supported AI apps use your Obsidian notes and propose improvements for your review. Read relevant sources in your running vault, inspect a correction or move in Smart Inbox, adjust supported wording when useful, and decide what to apply. Available tools depend on your installed plugins and permissions; other enabled tools can write directly. Explore examples.

The Inbox supports complete-note merges with native link handling and one final confirmation. Changes by file separates source removals from destination insertions, while matching move labels connect transferred passages. Corrections offer Inline, Compare and read-only reference evidence. A pending full-note merge can refresh after its source changes while preserving a rewritten insertion. The Local MCP port is also configurable. See the Inbox guide for the controls and limits.

Use Obsidian Desktop 1.12.2 or later, enable Connect Pro, and keep its required Pro access active. Keep the intended vault open. Your AI app must support the connection you choose.

Obsidian CLI is needed for Smart CLI and native CLI operations, not every Local MCP Smart action. Start with the setup guide.

No. Desktop apps (Local MCP) runs independently of the shared Connect session. The ChatGPT plugin and legacy GPT both use that remote session. Turning off ChatGPT plugin stops Remote MCP without disconnecting the shared session; Disconnect in the Connect session row stops both remote routes. Starting or stopping Local MCP does not change the remote session or disable direct Smart CLI use.

The installed plugins and channel permissions determine the tool list. Check Tools > Manage tools > Smart actions and the tools exposed in your app, rather than assuming every documented example is installed. The documentation identifies each example's requirements.

No. Standalone CLI tools (MCP) in Tools > Manage tools controls dedicated native MCP tools. On Local MCP, the Obsidian CLI dispatcher (Local MCP) can keep a native command reachable through obsidian_cli when its Local MCP switch is on, even if the standalone tool's switch is off. Remote MCP intentionally excludes that dispatcher regardless of the broad switch; only individually enabled, eligible dedicated native Tools can provide native-command access there, each with its command fixed internally. Remote GPT's native command access is separate too. Understand the permission boundaries.

No. Dedicated proposal tools always defer their source changes to Inbox review. Review > Review Obsidian CLI writes, which defaults to Off, can also queue Connect-mediated native CLI writes. Read-only native calls still run normally, and unrelated enabled write tools can still act directly. Exact create/inline-append plans show file changes; other native writes show a captured command and parameters. A native-call History label of Approved records approval, not proof that its intended result succeeded. Your AI app's confirmation dialogs are separate. Read, propose, or change.

That is the intended result: status: pending, source_files_changed: false, and a saved item key. Use Inbox in the Connect Pro settings header to inspect it. Notes change only when that proposal is applied. Do not repeat the request just because it is waiting for your decision.

Use propose_correction for one exact claim supported by reference evidence, propose_move_excerpt for a passage or an explicit complete-note merge, propose_move_blocks for complete selected blocks and their children, or propose_edit_set for related replacements, insertions, and new notes that need one coordinated review. An edit set does not rename or delete files. A move removes content from its source; only a full-note merge with delete_source_file: true moves the original file to trash. Compare the tools and review steps.

Yes. Use propose_move_excerpt with a whole-note source key, a destination in another file, and delete_source_file: true. The destination can be an existing or new note. Review the complete source and destination before approval; the destination is saved and verified before the intact original moves to trash. Ordinary excerpt and block moves retain their source notes, and metadata is not automatically reconciled. See complete-note merge inputs and review.

Yes. Use Edit replacement text for a correction or Edit proposed text for an excerpt, full-note insertion, or edit set. You can also change a move's destination or reorder its originally selected blocks. Placement, exact line anchors and source replacements stay fixed; changing them requires a new proposal. Done editing keeps a local review draft. In an edit set, Remove edit separately confirms removal of one saved operation while retaining the others; removing the final edit removes the proposal without changing notes or recording rejection. Finish editing and inspect every remaining file before deciding. A Viewed label means its comparison was opened, not approved. See the review controls.

Use Changes by file to identify each affected note and its outcome. Select a blue move label to highlight the corresponding source and destination passages. Red and green changes distinguish rewritten wording; unchanged source context stays neutral. Replacement at source identifies any continuity text left behind. For corrections, expand Captured evidence and choose Inline or Compare. Inspect the current review layouts.

Choose Approve. The final confirmation lists the effects, affected files and link consequences. Cancel returns to the pending review without applying changes. Review and confirmation.

A complete-note merge that removes its source includes native Obsidian link handling, including older pending proposals. Your existing Obsidian preference determines whether updates are automatic or prompted. Read the link-behavior message and final confirmation; reference handling happens during execution, not in a preflight scope table. Some references and heading or block targets may need attention. Native retargeting is not automatic anchor repair, and unavailable link support does not block the content merge. Ordinary excerpt and block moves do not retarget whole-note links. Watch a merge and follow its updated link.

The content merge remains applied and links remain unchanged. Unavailable support or a link-update failure also leaves the content merge applied. The Inbox records merge and native-link results separately. Do not apply the merge again to retry links; inspect the result and use any available link-only review or retry action. Link consequences.

Not for a pending complete-note merge. Reopen it or use its available source-refresh control. An untouched, unchanged insertion follows the current source; a rewrite or explicit review draft stays preserved. Compare the original source snapshot with the current source separately from the destination insertion, then deliberately incorporate anything the preserved insertion still needs. If files change after confirmation, the stale merge stops and refreshes for another confirmation. Nothing is applied again automatically. A partial excerpt or selected block that no longer matches still requires a new proposal.

Yes. Use Change destination to choose a new note, or supply an absent vault-relative .md or .txt path as to_key when creating the proposal. For tool requests, follow the destination arguments in the tool reference. The review marks a new note Creates file and Created on approval. Once captured, a missing existing target or newly occupied creation path is an error, not permission to switch modes or invent a missing section.

An exact, still-valid pending repeat returns its existing key with deduplicated: true. A similar idea is not necessarily a duplicate, and changing only its reason or group does not update that item. Inspect an existing review or recovery warning before retrying. Pending-result details.

Choose All pending, Ungrouped or a named group to narrow the queue. Grouped items still have independent review actions and decisions. History shows applied and rejected decisions, newest review first. Next proposal leaves the current item pending. On an eligible rejected item, Return to Pending reopens the same proposal for fresh review without changing notes or carrying forward consent; applied items cannot be restored this way. Storage, recovery, or execution records can block restoration. Inbox overview.

Yes. Open the ellipsis Proposal actions menu, select Delete proposal..., and confirm. This removes the review item without recording rejection feedback or changing source notes. Use Reject proposal when you want to retain the declined decision in History.

Yes, when that app has a supported connection and access to the updated note. Ask it to read the note and use the current information in its next task. The note is the shared source; Connect Pro does not transfer an assistant's private memory or guarantee that later requests retrieve it automatically. Continue from an updated note.

Yes, through the enabled get_proposal_feedback tool. It can retrieve one item or filtered pages of saved proposals and decisions. It does not read current notes or authorize another change. Feedback fields and examples.

No. Saved review decisions can inform a related proposal, but they do not automatically teach an assistant your preferences. A recorded rejection explanation is your feedback on that proposal; without one, rejection only means the whole proposal was declined. proposal_reason is the app's rationale, not your explanation. Current instructions and current notes still guide the next request. How to interpret feedback.

Follow the requirement shown in the review. You may need to finish editing, refresh a stale comparison, inspect a changed source, or choose a different new-note path because that path now exists. Full-note merges can keep the same pending proposal; partial excerpts and selected blocks need a new one when their original selection no longer matches. A manual-recovery warning needs separate attention. Link-update availability is a separate execution outcome, not a content-review approval gate.

An application attempt left file changes or the saved decision unresolved. Inspect the named files and review state before trying another change. The item remains blocked; inspecting or rejecting it does not restore files or clear that requirement. Recovery guidance.

The Inbox has no Undo command. Use your backup or version-history workflow. Native link updates for a complete-note merge are not an Undo operation or universal anchor repair. Recovery after a failed application is not a guarantee of complete rollback, and History is a record of decisions, not a restore mechanism.

Open Connect Pro stats from the Connect Pro status-bar menu, or run Smart Connect Pro: Open: Connect Pro stats. Select Refresh to update the overview, including approved proposals, changed words, returned words, and decisions by proposal type.

These are current saved outcomes, not a lifetime decision log. Returning a rejected proposal to Pending removes it from reviewed and rejected totals. See the Stats reference.

Words changed adds words inserted and removed in measured approved operations. A move counts at both locations, so this is not net note growth. Automatic backlink updates are excluded. Words returned to callers counts inline text in tracked connector responses; repeated reads count again, while attachments, binary data, and object keys are excluded.

Check What these numbers include and the measured-proposal fraction. Word and size totals exclude approved proposals whose saved text cannot be measured. Earlier completion records may include forwarding and omit failures; their returned-word totals cannot be recovered. See measurement coverage.

Yes. In Connect Pro stats, select Refresh, then Copy summary. After Summary copied with measurement coverage. appears, paste into your note. The summary includes totals, available change-size statistics, and a concise coverage explanation.

Keep that explanation with the numbers when sharing them. See Copy a progress summary.

No. Advanced > Tool requests > View requests shows retained completed request payloads from the current Obsidian session. It can include note content and does not show every failed attempt. Inbox History saves applied and rejected proposal decisions. An empty list does not rule out a failed request; a pending proposal is not an applied change.

The unified Inbox uses its own saved items. It does not import or modify the earlier separate contradiction, Extract, or Merge stores; existing imported native items remain. Refresh your app's tools and use the current proposal names. Inbox tools.

No. Local MCP describes where the server runs, not where your AI model processes data. An app may send inputs and returned content to its provider. Use tools and sources you are comfortable sharing, and review tool access.

The dedicated GPT is separate from Local MCP. It needs access to the supported GPT integration, an active Remote GPT session, and your desktop vault running. A local server alone does not make the vault available remotely. Remote GPT setup.

Check the Connect session row in the intended running vault. Resolve any sign-in, Pro access, or session-conflict message, and inspect Advanced > Obsidian CLI integration when commands are unavailable. Follow Remote GPT setup; turning Local MCP on will not fix that separate connection.

No. Smart Chat provides its own in-Obsidian conversation experience. Connect Pro makes enabled vault tools available to an external client or Smart CLI. Inbox review applies to dedicated proposals, not every operation performed by either plugin.

Do not assume an older connection has been migrated. Configure and test the replacement before removing a working setup. Connection migration is separate from importing old Inbox records. Current setup instructions.

Not as configured here. Its loopback-only endpoint is for a local app and does not require authentication. Do not publish it or forward it to the internet. The local listener is not a hosted public MCP or OpenAPI service.

Use the current Connect Pro plugin and its setup guide for this workflow. Older Smart Connect app instructions describe a different setup and should not be mixed with these connection steps.

Connect Pro documentation | Getting started | Pro Plugins FAQ