Co-Editing Basics
Co-Editing Basics

How live co-editing, presence, and automatic merging work.

When several people open the same branch, their edits sync in real time. IOModel uses conflict-free replicated data types (CRDTs), so concurrent changes merge automatically without manual conflict resolution.

What you get

FeatureBehavior
Live syncEdits appear for everyone almost immediately
PresenceSee who else is active in the project
Automatic mergeConcurrent edits combine without conflicts
Per-branchCo-editing happens on the branch you have open. Collab shares one live copy among members. Standard / Protected give each editor a personal main* working copy.

How it works

Open a branch

Everyone editing the same branch shares its live working copy.

Edit together

Models and specs update as people type; there is no manual save-and-reload.

Concurrent changes merge

CRDTs reconcile simultaneous edits automatically, so there is no “last write wins” loss.

No manual conflicts while co-editing

Because concurrent edits are merged automatically, you do not resolve conflicts during live co-editing. Conflicts only matter when comparing diverged branches — see Conflict Resolution.

Presence

Presence shows who is currently active so you can coordinate without interrupting each other.

Pair live editing with a quick verbal or written agreement on scope. Real-time editing removes file-locking friction, but a shared plan still prevents two people redoing the same work.

Last updated on