Use this when a Vault already exists in Git and Codex can access your local filesystem.
This path requires Codex CLI 0.121.0 or newer.
Add the Vault Sync marketplace:
codex plugin marketplace add graphlit/vault-syncAfter install, use the marketplace name graphlit-vault-sync for maintenance:
codex plugin marketplace upgrade graphlit-vault-sync
codex plugin marketplace remove graphlit-vault-syncThen ask Codex:
Use the Vault Sync plugin to set up my Vault from <your-vault-repo-url>.
Codex should install vault-sync, initialize the local folder, run vault-sync doctor, and ask before installing a recurring pull schedule.
If plugin marketplace support is not available in your Codex CLI version, install the skills directly:
npx skills add graphlit/vault-sync --skill vault-sync-setup
npx skills add graphlit/vault-sync --skill vault-sync-useYou can also point Codex at the direct skill entrypoint:
https://raw.githubusercontent.com/graphlit/vault-sync/main/skill.md
git clone https://github.com/graphlit/vault-sync
cd vault-sync
install -m 0755 bin/vault-sync ~/.local/bin/vault-sync
vault-sync init <your-vault-repo-url> ~/vaults/<name>
vault-sync schedule install ~/vaults/<name> --every 5mAfter setup, Codex should read README.md in the local Vault first, ignore hidden control folders, and inspect Markdown files directly with normal filesystem tools.