Sharing a PC: do Swarmbot scripts and skills mix when you switch accounts?
Swarmbot 1.2.152 separates app skills, scripts, AI memory, and menu preferences by account. Learn what changes when you sign in as someone else, what remains shared on the computer, and how teams should switch safely.
Starting with Swarmbot 1.2.152, switching Swarmbot accounts on the same computer loads a separate workspace for app skills, scripts, AI memory, and menu preferences instead of carrying over the previous account's content. This is useful for a studio or team sharing one PC, and for one person who keeps personal and business work under different accounts. Upgrade first, let the current account complete Cloud Sync, then sign out and sign in with the other account.
This guide was checked against the public Swarmbot 1.2.152 release. View the current public release. 阅读中文版
What changes with the Swarmbot account
Swarmbot creates a separate local workspace for the verified signed-in account. When you switch accounts, the client reloads that account's own content:
- App skills: local drafts, installed apps, enabled state, and AI visibility;
- Scripts: script projects and related execution records;
- AI memory: memory text, tags, state, and relationships;
- Interface preferences: device context menus, the Dock, stream-side shortcuts, favorite URLs, stream quality, and Device Wall ordering, card size, and displayed fields.
If account A hides an action from its Dock, account B does not have to use the same layout. A script or skill created by account B does not appear in account A's list. Returning to account A restores its local content and sync state; signing out does not delete that workspace.
If you are still deciding when to use AI, an app skill, or a script, see how Swarmbot combines AI, app skills, and scripts.
What still belongs to the computer
Account workspace isolation does not turn the computer into a completely new Swarmbot installation. These remain machine-level resources:
- discovered and registered devices;
- USB, Wi-Fi, ACC, and other device connections and states;
- device discovery subnets;
- machine runtime configuration and local paths.
Account B may therefore see devices that were already connected on the computer. Before acting, check the target device and current authorization again. A new script list does not imply that the device list is private to the new account.
Temporary device selection, the Batch Sync switch, window positions, and machine paths are not uploaded as account preferences either. They are intentionally not restored on another PC, because a temporary operating state on one machine should not become the starting state on another.
A safer account-switching routine for teams
Before signing out
- Finish running scripts, installations, file transfers, and batch jobs.
- Open Cloud Sync in Personal Center and check that important content is not still marked as local only.
- Note which account is active, then sign out.
After signing in
- Wait for the account workspace and Cloud Sync state to load.
- Open My App Skills and the script list to confirm that the content belongs to the current account.
- Check the Dock, context menu, and stream shortcuts for the expected layout.
- Select the devices for this task again.
- Run one low-risk check before starting a large batch.
During an account change, Swarmbot stops the previous account's sync cycle and prevents late background results from being saved into the new workspace. Users should still avoid starting another job after selecting Sign out. Wait for the new account's interface to settle before continuing.
How isolation and Cloud Sync work together
They solve different problems:
- Workspace isolation keeps account A and account B's skills, scripts, memory, and layouts separate on one PC.
- Cloud Sync restores one account's content when that same account uses another computer.
For example, account A can create a skill at the office and retrieve it at home after sync. Account B does not gain access to that skill merely by signing in on either computer.
For the exact content included in synchronization, read the Swarmbot Cloud Sync guide.
Where older content goes after the upgrade
During upgrade, Swarmbot uses the ownership already recorded by the previous Cloud Sync state to move historical resources into the original account's workspace. Signing in with another account first does not assign the old scripts and skills to that new account.
If old data does not contain enough evidence to identify an owner, Swarmbot keeps the files but does not automatically grant them to whichever account signs in next. If content appears missing:
- sign out and return to the account that used the previous version;
- inspect Cloud Sync in Personal Center;
- check the app-skill and script lists;
- if content is still missing, preserve the current data directory and logs before contacting support.
Do not repeatedly uninstall, clear the data directory, or import the same package into several accounts while trying to recover it. Those actions make the original ownership harder to diagnose.
Is this complete privacy isolation?
No. Swarmbot workspace isolation prevents its skills, scripts, memory, and preferences from being mixed accidentally. If several people use the same Windows sign-in, however, they still share the operating-system file environment as well as Swarmbot's machine-level device library and connection configuration.
If users should not be able to access one another's local files, or the computer handles sensitive customer material, create separate Windows users instead of relying only on Swarmbot account switching. Microsoft likewise recommends separate Windows accounts on shared computers so each person has distinct settings, documents, and apps, with a clearer boundary between personal and work data. Read Microsoft's Windows user-account guidance.
A practical rule is:
- switch Swarmbot accounts under one Windows user when trusted teammates need separate business workspaces;
- use separate Windows users when you need a stronger boundary around local files and sign-in sessions;
- give untrusted external collaborators limited device sharing rather than access to the computer.
Common questions
Why does a new account show only built-in skills?
That is expected. A new account does not inherit the previous user's local app skills. Wait for its own Cloud Sync, or import content from Skill Market or a local package for that account.
Why has the old layout not appeared immediately?
Wait for the preference snapshot to load, then reopen the relevant menu or stream. Synchronized stream quality is used the next time a stream opens; Swarmbot does not reconnect an active stream just to apply that preference.
Why are the devices still visible after switching accounts?
The device library and connections belong to the machine, not to an account workspace. Recheck device numbers, groups, and connection type before every important operation.
Can two people stay signed in simultaneously in one client?
One desktop client has one active Swarmbot account workspace at a time. For genuinely simultaneous use, use different computers or Windows user sessions instead of repeatedly switching one open window.
The short version
A Swarmbot account switch separates skills, scripts, AI memory, and personal menus, but it does not replace the computer's device library. Trusted teammates can use it to keep business workspaces apart; pair it with separate Windows users when local-file privacy also matters.