Sync devices
Lotti Sync keeps supported data aligned between your devices. Each device has its own local database; Sync moves changes through the configured sync account and catches a device up after it has been offline. Sync does not move the system of record into a Lotti cloud: the configured Matrix service relays end-to-end encrypted payloads between your devices while each device retains its own local copy.
What syncs, and what stays put
| Syncs between your devices | Stays on the one device |
|---|---|
| Journal entries and tasks, and the links between them · categories, labels, habits, dashboards and measurables · AI providers, models and profiles (including deletions) · saved task filters · config flags · light/dark theme choice · device profiles · your Daily OS name · notifications and their read state · task agents and their links · AI usage records (tokens, cost, energy) | Text-to-speech voice and speed · pane widths · AI concurrency limits · agent throttle timers · day-planning exclusions |
Two details worth knowing. Not everything that syncs is journal data: your device profile and Daily OS name travel as device preferences and are exempt from gap detection. And derived numbers are never sent — a saved task filter syncs, but the task counts computed from it are recalculated on each device.
Open Settings → Sync Settings to see the available setup, health, and recovery pages. The number beside Outbox is work that has not reached the sync service yet.
See your devices
Settings → Sync Settings → Devices lists every session on your sync account — not only the unverified ones.
Sessions signed in with this account can be removed — except the one you are on. Devices paired the old way, each with its own account, can be verified but not removed.
Pair another device
Pairing is its own flow, with a code to compare and two steps that follow connecting. It has a page of its own: Add a device.
In short: on a device that is already connected, open Settings → Sync Settings → Devices → Add device and show the code. On the new device, open the same page and scan it. Compare the pairing check code on both screens before connecting — the QR code carries your sync account credentials, so it goes to your own device and nowhere else.
Verify the new device
Pairing connects the device; verification confirms that both devices are talking to each other without an unknown device in the middle.
Compare the emoji in person or over a trusted call. Select They match on both devices only when the complete sequence matches. If even one emoji differs, cancel verification and investigate the account and device names before trying again.
Name devices and advertise capabilities
This device — “Device name and capabilities” — identifies the current device to the rest of the sync group. Give it a name that distinguishes the physical machine, such as “Mission Control Mac” rather than “Desktop.”
The page also lists capabilities the device can provide, such as local audio transcription or local language-model inference. Known devices show what the other nodes most recently advertised. The listed capabilities are descriptive; the relevant AI profile must still be configured to use them.
Understand catch-up and backfill
Normal sync processes changes as they arrive. Backfill detects gaps in the sequence received from known devices and requests missing records again.
- Inbound is work currently waiting in the incoming queue.
- Missing is the number of known sequence gaps.
- Skipped is work the inbound queue abandoned after it could not be processed normally.
- Automatic backfill continuously requests recoverable gaps and is the right default for normal use.
- Advanced recovery contains manual controls for an investigation. Use it only after ordinary sync and automatic backfill have had time to settle.
A non-zero missing count is not automatically data loss: another device may still be offline, or the request may already be in flight. Investigate when the count remains unchanged while all expected devices are online.
Read Sync Statistics
Sync Statistics separates message volume from processing health. It is useful when data looks stale but the account still reports as connected.
The sent-message card groups Matrix event types. Top KPIs summarizes processed messages, failures, and scheduled retries, while the entity totals show which Lotti payload families contributed to that work. A rising processed count with stable failures is healthy. If failures repeat or retries never clear, check the outbox and the other device's connectivity.
Inspect the Outbox
The Outbox is the local queue of changes waiting to be sent. Filter it by state to separate active work from failures.
- Pending items are waiting for their turn.
- Sending items are currently in flight.
- Failed items exhausted their current attempt and remain available for inspection.
- Sent items have been delivered and are retained temporarily for diagnostics.
Use Retry all after the underlying connection or account problem is fixed. Remove a failed item only when you intentionally do not want that change to reach other devices. Removing it from the outbox is not a substitute for repairing the corresponding local entry or attachment.
Continue with Resolve sync conflicts when two devices edited the same entry independently, or Sync maintenance for database-level recovery tools.