Insomnia Desktop ↔ Insomnia Cloud: Deterministic Merge Behavior for Concurrent Offline Collection Edits

Integration Boundary

Insomnia Desktop and Insomnia Cloud synchronize API collections, environments, and workspace settings as JSON documents. Both components support offline editing with queued changes that sync when connectivity returns.

Unresolved Behavior

Public documentation does not specify the merge algorithm applied when two offline desktop instances modify the same collection before reconnecting. It is unclear whether the service applies a deterministic automatic merge (e.g., operational transform or CRDT), enforces last-write-wins, or surfaces a user-facing conflict resolution prompt. This gap affects teams that rely on predictable CI/CD promotion of API specifications across environments.

Constraints

Behavior may vary by desktop version, Cloud account tier, and whether the workspace is personal or team-scoped. Plugin scripts and request-level custom code are not guaranteed to sync, further complicating round-trip fidelity.

Questions

1. Does Insomnia Cloud apply a documented, deterministic merge strategy for concurrent edits to the same collection JSON, or is the outcome version-dependent?
2. When a conflict is detected, does the desktop client prompt the user for resolution, or does it silently accept one version?
3. Can an exported design file be used as a canonical source to verify merge fidelity after a sync cycle?