Cloud Sync — how it works

Cloud Sync keeps a space and a folder in a cloud drive in step, in both directions. It works like GitHub sync, but for SharePoint, OneDrive, Google Drive, Dropbox and Proton Drive.

Set it up

  1. Open the space and choose Synchronizations in its menu. You need edit rights on the space.
  2. Choose a drive. If the account isn't connected yet, the page takes you to Connections, where you sign in once with that provider, and then brings you back. A drive with no account says itself when it cannot be used right now: Folder on my Mac, for example, says so when your Mac is not answering.
  3. Pick the folder. Use a folder for this space alone: everything in it becomes part of the space.
  4. Choose the direction:
    • Both ways: the usual choice.
    • Space → drive: the drive is a copy for people outside the mesh; edits made there are ignored.
    • Drive → space: the drive is where people work; the space never changes the drive.
  5. Choose the first sync, which only matters when both sides already hold files:
    • Take the drive's files: what is in the folder wins.
    • Take the space's content: what is in the space wins.
    • Merge: identical files are matched, and every other file present on both sides is shown as a conflict for you to decide.
  6. Press Sync now. After that it runs every 15 minutes, or only when you press the button if you set the interval to 0. A drive that needs no account (a folder on this computer, Proton Drive) starts at 0; a folder on your Mac starts at 15 minutes and simply waits while the Mac is off.

What is synced

In the space In the drive
The space itself index.md at the top of the folder
A page Name.md, with its title and description in a short header
A typed record (a task, a contact, a booking page…) Name.md too: its fields in the header, a readable summary below
Code Name.cs
Pages under a page a folder Name/ beside Name.md
A document, image or spreadsheet in the space's files the same file, at the same place, byte for byte

Every page and record is a Markdown file, so the folder reads well in Finder, SharePoint, Google Drive or Dropbox, and you can edit a page in any text editor. Documents, images and spreadsheets stay exactly as they are. Edit on either side: the next sync brings the change across.

Never synced: the space's settings and access (anything whose name starts with _), threads, and anything you list in the source's Ignore patterns.

Google Docs, Sheets and Slides have no file of their own, so they are listed on the Sync page as not synced rather than silently skipped. Files larger than 250 MB are not synced in this version.

When both sides changed

If someone edited a file in the drive and someone edited the same page in the space since the last sync, Cloud Sync takes neither version. The Sync page lists the conflict with both versions, and you choose Keep the space's version or Keep the drive's version. Until then that one file waits and every other file keeps syncing. Nothing is lost while it waits.

Deleting works the same way. A file deleted in the drive deletes the page in the space at the next sync, unless someone edited that page in the space after the last sync: then the page is kept, and the Sync page says so.

A sync that would delete a lot at once stops and asks first: more than 10 files and more than half of what it synced, or everything because the folder suddenly looks empty. Nothing is deleted. If that is really what you want, turn on Confirm large deletion in the sync's settings and sync again.

Who can do what

Editing the folder with an AI agent

Every synced folder gets an AGENTS.md at its top. Coding agents such as Claude Code, Copilot, Codex and Cursor read it, so they edit the folder the way the space expects. Cloud Sync writes it once and never overwrites it, so you can add notes about your project.

Drives

Limits in this version