Moving to another computer? Use Swarmbot Cloud Sync for scripts, skills and AI memory
With the same Swarmbot account, Cloud Sync carries script repositories, app skills and their settings, and AI memory between computers. Learn what is included, how to check status and what still needs local setup.
Swarmbot Cloud Sync carries script repositories, user app skills and their settings, and AI memory to another computer signed in with the same Swarmbot account. It is useful if you work from more than one PC or are moving to a new machine. Start by opening Personal Center → Cloud Sync on the original computer and waiting for the Synced state. On the other computer, sign in with the same account and let the first sync finish.
This guide was checked against the public Swarmbot 1.2.144 release. View the current public release manifest.
What Cloud Sync includes
The current Cloud Sync screen divides account storage into three groups:
- Script repositories: the script name, description, parameters and project files;
- App skills and settings: apps you installed or created, local drafts, enablement and AI visibility;
- AI memory: saved long-term memory content, tags, status and relationships.
These are often the most time-consuming parts of a Swarmbot setup to rebuild. If you have turned a workflow into a script and configured an app skill for a particular AI role, signing into the same account on another computer avoids importing each item again by hand.
Built-in skill files arrive with the Swarmbot release rather than being uploaded as personal content. Your enablement and visibility overrides for built-in skills can still follow the account. Secrets such as provider keys are not ordinary skill resources and must be configured where required on the new computer.
For a broader explanation of how these pieces fit together, see the Swarmbot skill import checklist and the developer overview.
First use: check the state instead of clicking repeatedly
After you sign in, the backend schedules an initial sync and continues checking periodically. Changes to local skills, scripts or memory also schedule another pass, so normal use does not require constant manual refreshes.
You can inspect Cloud Sync in two places:
- the Cloud Sync capacity area near the bottom of the left navigation, which shows usage and state;
- Personal Center → Cloud Sync, which breaks usage down by scripts, skills and memory and shows the last completion time.
Use Sync now when you want an immediate check, then return to View status after a short wait. A message that the sync was requested means the job was queued, not that every item was already transferred.
A safer sequence when changing computers
On the original computer
- Sign in with the Swarmbot account you normally use.
- Open Personal Center → Cloud Sync.
- Select Sync now.
- Wait for Synced and make sure there are no items marked as local only.
- Note the last completion time before shutting down or signing out.
On the new computer
- Install the current Swarmbot client.
- Sign in with the same account.
- Open Cloud Sync and wait for the first sync to complete.
- Check a few important items in Script Development, App Skills and AI Memory.
- Reconfigure anything that depends on provider secrets, external services or local paths.
- Run one small, low-risk task before returning to production work.
A successful content sync does not make two computers identical. Local files, external programs, sign-in sessions and device connections still need their own checks.
Understanding the status labels
- Synced: there are no local items waiting to upload.
- Syncing / Pending: work remains in progress; check again shortly.
- Storage full: new or enlarged items may remain local until content is cleaned up or an administrator changes the allowance.
- Account mismatch: this installation directory was previously associated with another account. Swarmbot pauses sync rather than uploading the previous account's local content.
- Sync error: read the specific message. If it points to an app-skill conflict, use the shortcut to open App Skills, resolve the local version, and sync again.
The local only count matters. It means those items have not reached the account storage yet and should not be expected on another computer.
What if two computers edit the same item?
Swarmbot resolves the same cloud item by its latest saved time. If two computers edit the same script, skill or memory at the same time, the later save can replace the earlier one.
For important work, finish an edit and wait for sync on one computer before continuing on the other. Swarmbot can preserve a recoverable local copy or show a conflict message in some app-skill cases, but that is not a substitute for deliberate version management. Keep an exported copy before a major script rewrite.
This is also why synchronization is not the same thing as a historical backup. General cloud-sync products propagate additions, changes and deletions between locations; Microsoft's OneDrive documentation describes that behavior directly. Read the sync explanation. Swarmbot Cloud Sync is designed to keep account content consistent, not to retain every past revision forever.
What Cloud Sync should not decide for you
- Do not put passwords, tokens or provider keys in skill instructions or example script values.
- Do not assume that a script appearing on another computer means all runtime dependencies are ready.
- Keep an independent copy before deleting important work.
- If you switch Swarmbot accounts, handle the Account mismatch warning instead of forcing the same data directory to continue.
- If storage is full, do not assume a growing local queue will eventually upload without action.
The workflow to remember
Confirm Synced on the old computer, sign into the same account on the new one, then inspect scripts, skills and memory. Configure secrets, local files and external programs separately. Cloud Sync moves the supported work products while you retain control of the machine-specific environment and sensitive information.