Cloud Sync & Collaboration
Real-time cloud sync with conflict resolution, presence indicators, save-to-cloud modal, and auto-sync for team collaboration.
How Sync Works
VortexHQ uses a version-based sync system with real-time WebSocket updates:
- Local persistence — Every change is immediately saved to your local disk (clusters, nexuses, and tabs survive restarts).
- Cloud push — For cloud clusters, changes are pushed to the server with a 60-second debounce. This batches rapid edits into a single sync.
- Real-time receive — When another team member pushes a change, your app receives it via WebSocket and updates the cluster automatically.
- Version tracking — Each cloud cluster has a version number. On push, the server checks that your version matches — if not, a conflict is detected.
Save to Cloud
Click the Save to Cloud button (or use Cmd+S on a cloud cluster) to open the save modal:
- Cluster/folder tree — Pick a destination cluster and folder for unsaved requests
- Inline new cluster creation — Create a new cluster directly from the save modal without leaving your work
- The save button reflects the current state — grayed out when clean, accent-colored when dirty
Dirty Tracking
VortexHQ tracks changes at both the tab level and the item level:
- Tab dirty dot — A dot indicator appears on the tab when there are unsaved changes to the request configuration
- Cloud dirty — Separately tracked. A snapshot of each tab's state is taken on save; any deviation from the snapshot marks the tab as cloud-dirty
- Save button state — Dynamically updates to show whether the current tab needs saving
Conflict Resolution
When two users edit the same cluster simultaneously and both push changes, a conflict occurs. VortexHQ displays a conflict banner with two options:
| Option | Behavior |
|---|---|
| Accept Remote | Discards your local changes and applies the remote version from the server |
| Keep Mine | Force-pushes your local version, overwriting the remote changes |
Auto-Sync
On startup, VortexHQ automatically:
- Joins WebSocket rooms for all cloud clusters (with a 2-second delay for connection stability)
- Syncs all cloud nexuses and their clusters
- Restores tab states including dirty indicators
You can also manually trigger Sync All from the nexus context menu, or Sync from Cloud on an individual cluster.
Presence System
Cloud clusters show presence indicators — small avatar circles in the cluster header of the sidebar tree. These show which team members are currently viewing the same cluster. Up to 3 avatars are displayed; additional members show an overflow count (e.g., “+2”).
Real-Time Events
VortexHQ handles these cloud events in real-time:
- Cluster created — Auto-imported into the relevant nexus
- Cluster updated — Merged with local data (version check)
- Cluster deleted — Removed from sidebar, associated tabs closed
- Member joined — Notification + presence update
- Invite received — Appears in the workspace dropdown
- Fork notification — Toast when someone forks your public cluster
Notifications
All collaboration events appear in the Notification Center (bell icon in the global header). Up to 80 notifications are kept in a FIFO queue with type-specific emoji icons. Actionable notifications link directly to the relevant view.