Sign in 中文

Cloud Sync

Using Cloud Sync

Cloud Sync is optional in the local-first Unfour desktop app. Sign in with an active Pro entitlement, then enable it for the workspaces you want to sync. API Client, SSH, Database, and MCP remain free and open source.

Enable sync for a workspace

  1. Open Settings → Account in Unfour and sign in. Check that Pro access is active; use Refresh account if the status has changed.
  2. Review the data boundaries below before uploading. Remove secrets from scripts, command templates, descriptions, and other shared text.
  3. Open Settings → Cloud Sync and ensure Sync service is on. From the workspace menu, choose Enable Cloud Sync, review the scope, and select Enable & Upload.
  4. Use View Sync Status from the workspace menu to inspect the last sync, pending changes, and issues. You can pause a workspace or pause all syncing with the Sync service switch.

What is synced

Cloud Sync exchanges selected records, not a copy of the local database. Names, hosts, usernames, descriptions, and ordinary values can still be confidential even when they are not credentials.

Workspace

Name, environment type, MCP policy, identity, timestamps, revisions, and deletion state. General app settings and workspace layout are not part of this record.

API collections, folders, and saved requests

Tree structure, names, order, method, URL, authentication metadata, headers, query parameters, body and body type, plus saved pre-request and post-response scripts. Recognized secret fields are redacted as described below.

Variables and environments

Environment names and ordering; variable keys, flags, descriptions, ordering, and non-secret values. A variable marked isSecret syncs its metadata, but not its value. An ordinary variable is not excluded just because its name sounds sensitive.

SSH and Database connections

Shared name, type, host, port, and timestamps. SSH adds username and authentication method. Database adds driver, database name, username, SSL mode, and read-only setting. Credentials, credential references, and advanced device-local configuration are excluded.

SSH tasks and steps

Task names, descriptions, order, and step definitions, including command templates, remote paths, and execution options. Concrete local upload/download paths become placeholders; portable variable templates can sync. Task connection/environment bindings, run inputs, results, and logs stay local.

What stays local

  • UI preferences, tabs and layout, activity, diagnostics, caches, active workspace, active environment, default workspace, and last-opened state.
  • API request/response history, database query history and results, saved SQL, SSH terminal and command history, task runs and logs, and transferred file contents are not Cloud Sync entities.
  • OS-keychain credentials and connection credential references; SSH private keys and key paths; SQLite files and local file paths. Configure credentials and paths again on each device.
  • Values explicitly marked secret in workspace/environment variables. A pull preserves an existing local secret where applicable; a new device may have an empty value until you enter it locally. These variable values are stored locally without encryption; the secret flag is not a keychain or encryption feature.

API and free-text secret handling

API snapshots redact secret authentication values, recognized sensitive headers and query keys, URL passwords and sensitive URL query values, and recognized secret fields in JSON and form bodies. Authentication type, placement, key name, and username may sync. Pulling a redacted field can preserve its existing local value; a new device may need that value re-entered.

Push, pull, retry, and deletion

  • Local changes in enabled workspaces enter a persistent upload queue. The background worker pulls remote changes and pushes pending local changes, with periodic pulls; it is not a real-time co-editing session.
  • When offline, you can continue local work. Retryable failures retain queued changes and retry after connectivity returns while the app is running, the service and workspace are enabled, and account access is valid.
  • Conflicting edits need a choice between the local and cloud version. Open View Sync Status or Resolve Sync Issue and review Use this device / Use cloud. This is not an automatic field-by-field merge.
  • Deletions propagate as tombstones, including supported child records when a parent is deleted. A remote deletion can conflict with a local edit. Accepting the cloud deletion removes the corresponding local record; keeping local data may require resolving related parent conflicts first.
  • Permanently rejected changes stop automatic retry and appear under Changes requiring recovery. Retry current local resubmits current local state. Use cloud can discard that local change and may be unavailable when a safe replacement cannot be made. Back up important local work before destructive recovery; Cloud Sync is not a versioned backup.

Open a workspace on another device

  1. Install the same official Unfour app on the other device and sign in to the same account with active Pro access.
  2. Open Settings → Cloud Sync → Open Cloud Workspace. Choose an available workspace and select Download & Open; do not create a duplicate local workspace as a substitute for this action.
  3. Re-enter missing secret values, attach local credentials and key/file paths, and check task bindings and the active environment before executing requests, commands, or SQL.
  4. Let pending changes settle and inspect conflicts before switching devices. Review the workspace MCP policy too: that policy is shared data, unlike the active-workspace selection.

Personal Pro and device limits

Personal Pro covers 1 user on up to 5 devices. Use your own account on those devices; this is not a shared team subscription. Automated device-count enforcement is not currently enabled, but the license limit still applies. Pricing and subscription terms come from the shared billing configuration; the trusted account service decides entitlement.

Troubleshooting

Sync does not start

Check Settings → Account, active Pro access, Settings → Cloud Sync → Sync service, and whether this workspace is enabled. Refresh account if the local sync context could not initialize.

Signed in, but Pro is not active

Confirm that the desktop and website use the same account. Check the website Account page and use Refresh account in the desktop app. A completed checkout redirect alone is not proof of an active entitlement.

Pending or offline

Inspect View Sync Status for the last sync and pending count. Check connectivity; Retry is shown in the offline state. Resume paused service/workspace syncing and sign in again if the session-expired message asks you to.

Needs attention or conflict

Review the local/cloud choices and any rejected changes. Ordinary Retry does not resolve a conflict or permanently rejected change. Do not discard local changes unless you intend to replace them.

Download or connection fails

A local workspace with the same name may need renaming before download. On a new device, missing credentials, local paths, secret values, or task bindings must be configured locally. Follow a protocol-version error by updating Unfour.

Still stuck

Use Advanced diagnostics in the workspace status dialog or Settings → Cloud Sync → Advanced → Copy diagnostics. Review the output before sharing it privately with support; do not include credentials or production payloads.