Documentation

Use your existing sync setup.

Use OneDrive, Google Drive, or an organization-managed file service to transfer your note files, with live updates for valid changes that do not conflict with local work.

Find the directories first

Open Settings → Files & sync → Files & storage. The desktop app shows the exact Application data, Notes and images, and Local recovery locations, with buttons to open them.

  • Have your sync setup include the specific active library directories you intend to transfer.
  • Confirm that your sync client and organization’s configuration support those locations.
  • A folder containing exports or backups can also be synced, but that does not synchronize the active library automatically.

Initialize the second computer

Use the current CQS version on both computers. Back up any existing destination library, then initialize the second computer using an export from the source workspace so both installations share the same workspace UUID.

Choose a complete set of files

Sync complete note directories, including their images and attachments. Unused label definitions and saved searches live in workspace state, not just the notes folder.

  • Syncing state.json also transfers calculation data, settings, and workspace identity, which creates more opportunities for conflicts.
  • Protected notes need the matching security files and keys. Transfer a complete library while the app is closed when those are required.
  • Keep local-safety, device identity, activation records, WebView storage, and semantic caches on each device.
  • Keep security/mcp and agent PEM credentials device-local. Create fresh grants on another installation.

Receive clean note updates while CQS is open

In Settings → Files & sync → External file changes, enable Watch external files and Automatically apply non-conflicting note updates. A complete, valid later version of a note in the same workspace updates that note in place when it does not conflict with local work. A clean open note refreshes without restarting the app or creating a copy.

  • Use the current CQS version on both computers and initialize them with the same workspace UUID. Complete new notes in that workspace can arrive through the same workflow.
  • Automatic clean updates can be disabled per device. The external sync service still handles file transfer.
  • Unsaved editor drafts stay intact. If the saved note has changed, use Save a copy to keep your draft separately or Reload saved note to return to the accepted version.
  • Encrypted or incomplete transfers wait until their contents and attachments can be validated. They are not automatically treated as conflict copies.

Review incoming changes

Ask before handling conflicts or other file changes and the import-copy/keep-current policy handle genuine conflicts. Automatic clean updates preserve the existing note ID; importing a reviewed conflict as a copy creates a separate note.

  • Keep current files retains accepted content and archives the incoming version.
  • Import selected notes as new copies creates independent notes; it is separate from a clean update in place.
  • Calculator-state and settings replacements use their own review workflow; they are not merged into the running app. Security files also need separate handling.
  • A valid note deletion record can propagate through the same workflow. A missing note.json file on its own requires review.
  • Pause a sync job that is repeatedly rewriting files during review, then recheck before continuing.

See when this computer received an update

The note metadata includes Last updated externally after an external update is accepted. It records when this PC received the update, rather than the note’s edit time on the other computer.

Within an organization

Have the organization choose the approved folder locations, who can access them, and how devices hand off the library. Sharing a directory shares the files in it; it does not create per-person CalciteQuickSolve roles or single sign-on.

  • Keep recovery keys separate from the library and limit access to protected material.
  • Grant MCP access separately on each device; a UI lock does not stop authorized agents.
  • Keep dated backups outside the active synchronized library, since sync can propagate unwanted changes.
  • For a simple transfer, a folder backup or secure note bundle may be easier than sharing an active library.