How sync works

Each pool is one linear revision log. Every browser applies the same log and converges on the same state.

The revision log

A Cloudflare Durable Object serializes all changes to a pool into one linear revision log. Each change — add a bookmark, move a folder, install an extension — becomes a revision. When two browsers change the pool at the same time, the server assigns one order, and every browser applies the same sequence.

Revisions are kept for 30 days. Within that window, you can undo the last change with one click or restore the pool to any revision.

Strict replacement

Sync is a mirror, not a merge. When a browser joins a pool, the pool state replaces its local bookmarks and user-installed extensions. There are no merge screens and no conflict prompts.

From then on, every browser in the pool holds the same data: the same folders, the same bookmarks in the same order, and the same extensions with the same enabled state.

Participation switches

Each browser has two switches: bookmarks and extensions. Turn one off to stop mirroring that data type in that browser. The browser keeps its local copy and stops sending and receiving changes for it. The other browsers in the pool are not affected.

What happens on re-enable

Turning a switch back on works like a fresh join for that data type. The pool state replaces the browser's local data. Local changes made while the switch was off are discarded.