Before you begin
- Each device is connected to the same Orchestris Server.
- You are signed in to the same organization and user account on each device.
Know what syncs and what stays on one device
A conversation synchronizes only when both devices use the same Orchestris Server, organization, and user account. Using the same email address on another server or organization does not join the histories.
| Data | Synchronizes? | Conditions |
|---|---|---|
| Server-backed conversations and messages | Yes | Same server, organization, and signed-in user |
| Project names and conversation assignments | Yes | The Project and conversation belong to the same server and organization |
| Eligible uploaded attachments referenced by messages | Yes | The attachment finishes uploading before its message synchronizes |
| Direct-provider conversations | No | History stays on this device; prompts still go to the configured provider |
| Local-only conversations | No | History stays on this device; prompts still go to the selected server or provider |
| Privacy-mode conversations and local attachments | No | History is not saved as synchronized server history; prompts still go through Orchestris Server and the selected provider |
| Locally stored direct-provider credentials and Chat preferences | No | These settings remain with this app installation or browser profile |
- Data
- Server-backed conversations and messages
- Synchronizes?
- Yes
- Conditions
- Same server, organization, and signed-in user
- Data
- Project names and conversation assignments
- Synchronizes?
- Yes
- Conditions
- The Project and conversation belong to the same server and organization
- Data
- Eligible uploaded attachments referenced by messages
- Synchronizes?
- Yes
- Conditions
- The attachment finishes uploading before its message synchronizes
- Data
- Direct-provider conversations
- Synchronizes?
- No
- Conditions
- History stays on this device; prompts still go to the configured provider
- Data
- Local-only conversations
- Synchronizes?
- No
- Conditions
- History stays on this device; prompts still go to the selected server or provider
- Data
- Privacy-mode conversations and local attachments
- Synchronizes?
- No
- Conditions
- History is not saved as synchronized server history; prompts still go through Orchestris Server and the selected provider
- Data
- Locally stored direct-provider credentials and Chat preferences
- Synchronizes?
- No
- Conditions
- These settings remain with this app installation or browser profile
Wait for sync or request it now
- Chat starts syncing after it connects and you sign in.
- Remote changes can start a background sync automatically.
- Chat also retries about every 10 minutes. This is a retry interval, not a promise that every change appears within 10 minutes.
- Changes made while offline remain on the device until connectivity and sign-in recover.
- 1
Request an immediate pass
Select the sync icon in the conversation list. On compact layouts, open Conversation list actions and choose Sync now.
- 2
Wait for completion
The control shows Syncing while work is in progress. Its tooltip shows the last successful automatic sync time when available.
- 3
Check the correct scope
If an item is still absent on another device, confirm the same server, organization, and user are selected before retrying.
Review a Draft Conflict
If the same conversation changes in two places and Chat cannot combine the changes safely, it keeps both versions. The extra conversation has a title ending in (Draft Conflict), so neither version is silently discarded.
- 1
Open both conversations
Compare the original conversation with the conversation titled (Draft Conflict).
- 2
Keep the information you need
Continue from the preferred branch or manually copy required content into one conversation.
- 3
Remove the extra branch only after review
Delete the conflict branch when you are certain it is no longer needed. Conversation deletion cannot be undone.