A sync framework that keeps conversations, prompts, pinned memory, and per-device settings coherent across your laptop, your phone, and your desktop. Two reference domains land first (sessions and prompts); the framework is general enough that later domains plug in without re-engineering each one. Starting a conversation on one device, continuing it on another, stops requiring an explicit export step.
Later in 5.0.x
The naive way to ship cross-device sync would be to wire it once for conversations, then again for prompts, then again for pinned memory, then again for tenant settings. Each domain has its own data model, its own conflict-resolution rules, its own privacy posture — building it four times is four ways to get it subtly wrong.
The 5.0.x approach: build the framework once. Each syncable domain declares its data shape, its conflict-resolution policy, and its scope boundary. The framework handles the protocol — change events, conflict reconciliation, eventual consistency across offline-and-back-online — in one place. Adding a new domain becomes a per-domain config, not a per-domain rebuild.
Once those two ship with the framework as the substrate, later domains — pinned memory, per-device settings, knowledge-base preferences, plugin configurations — plug in via the same protocol without each one being an engineering project.
The sync protocol lives between each client device and the cluster. Devices do not talk directly to each other — the cluster is always the rendezvous, which means the customer's authoritative copy stays in their installation, not in a third-party cloud service. Offline edits queue locally; reconciliation runs when the device reconnects.
This page updates as each piece lands. The release notes are the formal cut.
For the chat shell today, see first run. For mobile apps, see mobile apps. For the full 5.0.x roadmap, see what's next in 5.0.x.