Continue on another computer
3 minute read · Cloud & Sync
Continue a project conversation on another computer without confusing synced history with a copied checkout. The local project folder and running processes still belong to their device.
- Connect the second computer
- Understand the sync state
- Open the same work on another computer
- Interpret the sync state
- Protect edits during recovery
Connect the second computer
Sign in to the same Vortex account and unlock its Vault. Let the workspace and conversation records sync. When a project needs a local folder, select the matching checkout on this computer, or clone the repository first.
Check the selected folder before starting an agent. A project name matching in the sidebar does not prove its local files are the same revision. Start the app locally after its dependencies and configuration are ready.
Understand the sync state
Pending or offline means local work still needs synchronization. Locked means the protected storage needs unlock. A conflict needs a deliberate resolution; preserve local typing and inspect the cloud version before choosing what to keep.
Workspace records contain encrypted content with version checks. The server also keeps nonsecret ownership and relationship metadata for quotas, safe sync and retention. A task lease identifies another device’s running work; it is not a remote-execution service.
Deleting a synced record leaves a tombstone so an offline client can learn about the deletion. Do not repeatedly recreate old content from a stale copy. Existing API sharing is a separate visibility choice from personal workspace sync.
Next: Vault recovery, storage and deletion.
Open the same work on another computer
Sign in to the same Vortex account and unlock its Vault. Allow the workspace and conversation records to synchronize. Then bind the project to the correct local folder on this device, or clone the intended repository before selecting that folder. Cloud project metadata does not transfer the full Git checkout, its dependencies or a running local app.
Open the synchronized chat and inspect its history. A live task lease may show that another device owns an active run. Reading that history does not move the provider process to your computer or grant a second simultaneous run. Let the owner finish or follow the app's explicit ownership controls.
Interpret the sync state
| State | Meaning and next action |
|---|---|
| Offline or pending | Local work may still need upload; preserve it and reconnect. |
| Locked | Unlock the Vault before encrypted records can be read or written. |
| Syncing | Transfers/version checks are still in progress. |
| Synced | The supported records are current for that completed cycle; this is not a full checkout backup. |
| Conflict | Compare the versions and keep local edits until resolution is deliberate. |
New writes authenticate record identity/version inside encrypted envelopes. The server stores explicit non-secret relationships and ownership metadata for quotas and synchronization without reading chat text. Older records can receive compatible metadata backfill without changing their encrypted content version.
Protect edits during recovery
Do not remove the local profile or clear history to dismiss a conflict. Keep a copy of recoverable profile data before investigating a migration or encryption failure. Local SQLite stores encrypted records and preserves migration recovery material; the database format is not permission to decrypt everything into plaintext.
Deletion synchronizes through tombstones so an offline device can learn that a record was removed. It must not blindly resurrect an old copy. For oldest-content cleanup, read retention and deletion before relying on cloud history as an archive.