Obsidian

From the CLI

bestmate connect obsidian ~/Vaults/Personal --dry-run

Drop --dry-run to actually sync.

Flag	Description
`--store <slug>`	Route notes into a specific context store
`--twin <slug>`	Override the target twin
`--folder <name>`	Only sync notes under this vault subfolder — repeatable
`--dry-run`	Preview what would be pushed
`--full`	Ignore the local sync cache and re-push every note
`--limit <n>`	Push at most N notes this run
`--quiet`	Minimal output, for cron and scheduled syncs

From the macOS app

Connections → Obsidian → Connect points at a vault folder on this Mac and opens a picker so you can choose which notes to sync.

Re-runs are incremental

Unchanged notes are skipped locally, and re-synced notes upsert rather than duplicating. Running this on a schedule is safe and cheap:

bestmate connect obsidian ~/Vaults/Personal --quiet

Use --full only when you want to force a complete re-push — after changing how notes are routed, for example.

Syncing part of a vault

Most vaults hold more than you want in a twin. Scope it:

# Just two folders
bestmate connect obsidian ~/Vaults/Work --folder "Clients" --folder "Decisions"

# Route client notes into their own store as they land
bestmate stores route acme --source obsidian --folder "Clients/Acme" --tag client

Large vaults

A big vault is fine — the sync batches and resumes. If you’d rather bring it in gradually, --limit caps each run and the rest go next time:

bestmate connect obsidian ~/Vaults/Personal --limit 200

Getting Started

CLI Reference

Platform

Integrations

macOS App

From the CLI

From the macOS app

Re-runs are incremental

Syncing part of a vault

Large vaults

​From the CLI

​From the macOS app

​Re-runs are incremental

​Syncing part of a vault

​Large vaults

From the CLI

From the macOS app

Re-runs are incremental

Syncing part of a vault

Large vaults