vault-sync-setup

To mirror a Git-backed Markdown Vault to local filesystem files, you initialize the repository in a local folder using the vault-sync init command. This clones the Vault content so your AI tool can read the notes directly from the filesystem without a live app connection.

Yes, you can automatically refresh local Vault content on a schedule by installing an optional recurring pull configuration. This keeps your local mirror current at a chosen interval for ongoing research or team workflows without manual intervention.

Vault-sync requires macOS, Linux, or WSL2 support to function properly. It relies on the availability of bash and git, meaning native Windows environments without WSL2 are not supported for this filesystem sync setup.

To keep your local Vault mirror current, you run the vault-sync pull command to fetch updates. This pulls new exports and committed edits from the upstream repository so your local reading context remains up to date.

The vault-sync doctor command verifies your local Vault mirror setup and checks the filesystem sync configuration. It ensures the repository is correctly cloned and that dependencies like git are available for ongoing pulls.

Yes, filesystem sync supports team workflows where exported notes and context must stay current. By mirroring the Git-backed repository and optionally scheduling pulls, the entire team can access updated local files for AI processing.