On this page
What the web editor uses today
Crux creates Yjs documents and shared text types, binds them to the editor, and uses y-webrtc to exchange updates between peers. Awareness messages carry presence information such as names, cursors and selections. Shared text and presence serve different purposes: a cursor is not the document itself.
The Yjs collaborative editor guide explains this separation between shared data, editor bindings and network providers. Crux follows that model for its web editing path.
From a local edit to shared text
- An editor change updates the local Yjs text value.
- The provider exchanges encoded updates with connected peers.
- Each peer applies the received updates to its own document.
- Editor bindings reflect the resulting text, while awareness updates show collaborator presence.
Network setup, reconnection and delivery matter as well as merge work. The live benchmark measures local update application on three replicas. It does not include WebRTC connection setup or promise a fixed convergence time across a network.
Text convergence and syntax are different guarantees
Two developers can make independently reasonable changes that produce a broken program when combined. A text CRDT can make every replica agree on those changes while a parser reports an error. It does not know which API design the team intended or whether a test should pass.
An abstract syntax tree represents language structure. A syntax-aware CRDT would need well-defined operations for that structure, support for temporarily incomplete code, and rules for competing transformations. Those requirements differ from synchronizing ordinary text.
Keep review and authorization explicit
Run the parser, type-checker and tests after shared changes, and review agent edits before committing them. Agreement between replicas is one check; application correctness is another.
A shared room identifier or an awareness name is not proof of a collaborator's identity. Share room links only with intended collaborators. Actions that spend money, execute another person's tools or disclose credentials need authenticated authorization beyond document synchronization.
For transport details and its configuration options, read the official y-webrtc documentation.
BUILD SOMETHING TOGETHER
Your team.
Your agents.
One workspace.
Bring your people, code and context together in Crux.
Join the waitlist