Live sync and presence
Live sync keeps open views current as workspace records and run state change. Presence shows which members are active, such as their current view or cursor. These features use the workspace’s access controls.
Subscribe to workspace changes
Section titled “Subscribe to workspace changes”Event and replay cursor
Section titled “Event and replay cursor”A client can use GET /api/v1/events for server-sent events or /api/v1/realtime for a WebSocket subscription. Use a short-lived, single-use secret minted by the server for browser clients. The runtime limits subscriptions to the credential’s topics.
{ "type": "gabriel.subscription.create", "topics": ["gabriel.resource.*"], "after": "evt_3f9c"}Example board refresh
Section titled “Example board refresh”A list update invalidates the affected board data. Load current state under the viewer’s permissions and retain the last handled event identifier as the replay cursor. When a connection resumes, request subsequent events. If the server sends gabriel.replay.reset_required, reload authoritative state before continuing. The profile leaves mandatory events for each resource type open.
Follow a team member
Section titled “Follow a team member”Presence scope and permissions
Section titled “Presence scope and permissions”Presence carries transient details such as a member’s active tab, canvas position, or pointer. Validate received state before applying it. Following can mirror a view within the follower’s access. Actions such as adding a playbook or joining a call require the follower’s own action. Keep presence separate from durable definitions, records, and run history.
See event transport and the presence and following proposal.