Skip to main content
A conversation that runs on your computer stops when the computer sleeps. Move it to the cloud and the agent keeps working on a copy of its folders, then bring the results back. Your organization’s Desktop policy has one switch for each direction, and you can turn either off for your computer in Settings.

Move a conversation to the cloud

  1. Choose Move to cloud in the computer strip under the composer.
  2. Pick the folders the agent needs: up to five, each up to 2 GB. The app uploads a copy of each.
  3. Choose Move to cloud.
The copy leaves out folders that are rebuilt anyway (node_modules, .venv, __pycache__) and anything private, such as keys and credentials, which never leave your computer. The next messages run in the cloud, on the copies. The folders on your computer do not change.
Move this conversation to the cloud dialog listing three folders with checkboxes, and Cancel and Move to cloud

Choosing the folders to take to the cloud. Shown with sample data.

Bring it back

  1. Choose Bring back in the computer strip. The app downloads the cloud copy, compares it with what it uploaded, and lists every change:
    • Apply: changed only in the cloud. It is updated on your computer.
    • New: created in the cloud.
    • Conflict: changed in both places. Choose Keep mine, Take the cloud version or Keep both (the cloud version is saved next to yours, for example README.cloud.md).
    • Deleted in the cloud: listed only. Nothing on your computer is deleted.
  2. Open any file to see what changed, then choose Apply changes. The conversation runs on your computer again.
4 changes from the cloud dialog: two files to apply, one conflict with Keep mine, Take the cloud version and Keep both, one new file, and two files deleted in the cloud listed only

Changes from the cloud, with a conflict to settle. Shown with sample data.

Nothing is deleted on either side. The cloud copy stays with the conversation after you bring it back.
The copy is stored in the conversation’s folder on the agent’s workspace disk, where the agent runs: xpander’s production cluster in AWS us-west-2 on xpander cloud, or your own cluster’s storage on Hybrid and Air-Gapped.Nothing deletes the copy on a schedule. Conversation retention does not remove it, and deleting the agent does not remove it. It stays on the agent’s disk until it is removed there. About 30 days after the last move, Bring back no longer finds the copy, although the files stay.

While your computer is offline

The app keeps one outgoing connection to your xpander and reconnects on its own: at launch, when your computer wakes, and when the connection goes quiet. Nothing on your computer accepts incoming connections. The computer status in the sidebar shows where it stands. Conversations that do not use your computer carry on as usual. For a task that needs your computer, the Desktop policy sets When the computer is offline (Ask by default): When your computer reconnects, waiting work continues. A scheduled task linked to your computer that fires while the app is closed runs in the cloud instead. To have agents work in the cloud first, so a conversation keeps going while your computer sleeps, turn Prefer this Mac’s files and apps off. See Prefer this computer or the cloud.

When the app cannot reconnect

Grey dot with Mac offline and the Mac's name

The status in the sidebar while the computer is offline. Shown with sample data.

  • Mac offline for a long time: check your network (and VPN for a self-hosted xpander), and the address in Settings.
  • Mac turned off or Mac removed: an admin turned Omni Desktop off for you or revoked this computer. After a revoke, sign in again to register the computer as a new device.
More fixes: Troubleshooting.