Liveblocks Sync and LiveText for human-agent collaboration
Liveblocks is positioning realtime shared state as infrastructure for both human collaboration and backend agents, which is close to the 'agentic web' product surface now emerging around collaborative apps.
Links: Original source · Shared link · Related link 1 · Related link 2 · Related link 3 · Related link 4 · Related link 5
Logged at IST: 2026-09-01 21:37 IST
What it is: Liveblocks Sync, a realtime sync engine for collaborative apps where humans and backend agents edit the same product state. The launch centers on LiveText, a new collaborative text data type positioned as simpler and more integrated than Yjs for many structured apps.
Gist: Liveblocks Sync packages the usual multiplayer hard parts: conflict resolution, persistence, reconnection, presence, optimistic updates, version history, multiplayer undo, auth/permissions, and server-side document editing. The agentic-web framing is that agents can connect from the backend over WebSocket or HTTP, show up with presence, edit alongside users, and stream workflow state into the shared room.
The interesting technical distinction is LiveText versus Yjs. LiveText lives inside the same Liveblocks Storage tree as LiveObject, LiveList, LiveMap, and LiveFile. For apps where text is one field among many, decks, canvases, boards, forms, or record-based tools, that means geometry, ordering, attributes, and words share one document, one API surface, one undo history, and one version snapshot. Server code can also read the whole structured document as ordinary data without attaching an editor or decoding a separate Y.Doc.
Yjs is still the right answer when the page itself is the document, the text can grow without a natural bound, or the app needs editor bindings and features LiveText does not yet cover. Liveblocks docs call out long-form documents, wikis, notes apps, code editors, subdocuments, and experimental browser persistence as reasons to stay with Yjs. LiveText currently supports Tiptap, BlockNote, ProseMirror, and CodeMirror, with each LiveText node capped around 2 MB.
Newsletter angle: Relevant to WebMCP/agentic-web thinking: shared product state is becoming a first-class substrate for humans and backend agents, not just browser-to-browser multiplayer.