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

Move a conversation to the cloud

  1. Choose Move to cloud in the laptop 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 Mac. The next messages run in the cloud, on the copies. The folders on your Mac 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 laptop 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 Mac.
    • 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 Mac is deleted.
  2. Open any file to see what changed, then choose Apply changes. The conversation runs on your Mac 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.