A vault that keeps syncing on a machine that never opens Obsidian is headless sync, and the app’s Command-line CLI page is its control room: install it, sign in, add vaults, start and stop each one. For what the tool is and the first setup, see Headless sync.
The vault list
Section titled “The vault list”One row per vault, each its own process: Start / Stop, Logs, History, Edit, Remove, and with several vaults Start all / Stop all.
- The state is Syncing, Waiting for another sync or Stopped, and the row says how many conflict copies this vault has.
- History is what this run has synced — the same log the plugin shows.
- Edit changes the device name and what the vault syncs. Markdown and canvases always sync; the other five file types are switches, and folders can be left out. The local folder is fixed: a different folder is a different vault.
One vault, one writer
Section titled “One vault, one writer”With Obsidian open on the same vault, only one of the two syncs: whichever started first, and the other waits. The row reads Waiting for another sync, and Obsidian’s status bar says the external sync service is syncing. The waiting side writes nothing and takes over by itself when the other one stops.
The tool itself
Section titled “The tool itself”The card above the list shows the installed version and offers Check for updates, Upgrade and Install from local file. An upgrade stops the running vaults first and starts them again after.
Logging out
Section titled “Logging out”Log out stops every vault’s process, then forgets this computer’s server address, user key and vault bindings. Local files and everything on the server are unchanged.