Getting started with Connect Pro
The first result is one bounded action whose ChatGPT response and vault-side result match.
Before you start
Make sure that:
- Obsidian Desktop 1.12 or later is running
- the intended vault is open
- Obsidian CLI is enabled
- Connect Pro is installed, enabled, and active
- your Connect Pro account and Pro access are current
- the Official Connect Pro GPT is available in ChatGPT
1. Connect the desktop vault
Open Connect Pro settings or its status control. Start the connection. Wait until the plugin shows a connected status. Make sure that Disconnect is visible.
Do not continue from an Active Store row alone. Active proves that the plugin loaded. Connected status and Disconnect prove that a session is ready.
2. Identify the intended vault
Open the Official Connect Pro GPT. Ask it to identify the connected vault. Make sure that the result names the vault you intend to use.
If the wrong vault is identified, stop. Open the intended vault in Obsidian Desktop. Reconnect. Identify the vault again.
3. Run one low-risk action
Select one read-only or easily reversible action exposed by the current connected surface. A test-note action is suitable when it creates one uniquely named note that you can delete after review.
Keep the request bounded:
- one vault
- one exact target
- one visible change or read result
- no unattended expansion
4. Compare both results
- Read the result returned in ChatGPT.
- Open the target in Obsidian.
- Make sure that the vault-side result matches the request.
- Make sure that no unrelated note, property, Base, or folder changed.
The first result is complete only when the ChatGPT response and the vault agree.
5. Disconnect
Select Disconnect when the workflow is complete. Make sure that the connected status ends. New vault commands must remain unavailable until you connect again.
If something is wrong
| What happened | Try first |
|---|---|
| Connect Pro is Active, but not connected | Open settings. Complete account and connection requirements. Connect again. |
| Disconnect is not visible | Treat the session as not ready. Reopen the connection control. |
| The wrong vault is identified | Stop before writing. Open the intended desktop vault. Reconnect. |
| The requested action is unavailable | Select one action exposed by the current connected surface. Do not broaden the request. |
| ChatGPT and the vault disagree | Stop. Examine the target and returned tool result. Correct the boundary before one retry. |
| An action from another device stops working | Make sure that Obsidian Desktop is running and Connect Pro remains connected. |
Continue after the first result
- Use the Connect Pro documentation for supported boundaries, approvals, remote-device conditions, and Smart CLI Pro.
- Use the Connect Pro FAQs for migration and public-integration boundaries.
- Expand from one target to a larger workflow only after the bounded result is repeatable.