Continue on another computer
4 minute read · Cloud & Sync
Vortex can synchronize supported workspace and conversation records. Changes from your other computers appear automatically while you are signed in. Unsent drafts stay on the computer where you typed them. Each computer still needs its own checkout, connected provider accounts and running services. Browser profiles and local execution are separate from synchronized history.
- Prepare the second computer
- Use the provider available here
- Understand the sync state
- See new messages as they arrive
- Keep active work on its owning computer
- Protect work during recovery
Prepare the second computer
- Sign in to the same Vortex account and unlock its Vault.
- Let the workspace and conversation records synchronize.
- Bind the project to its matching local folder, or clone the repository and then select that checkout.
- Compare the branch and revision before starting work. The same project name does not prove both computers have the same files.
- Connect a coding-agent account in Settings → AI providers and check the resolved provider and model in the chat.
Cloud project metadata does not copy dependencies, environment files, browser logins or the running application. Prepare and start the app on this computer when you want to use its local Preview.
Use the provider available here
Provider account choices are never synchronized. When a synchronized chat names a provider account absent from this computer, Vortex chooses a local account from the same provider, regardless of the account's name. If that provider is not connected here, it uses another connected provider account on this computer. The selection remains local and does not overwrite the other machine's choice.
For example, a chat using a Codex profile named “Office” can use a local Codex profile named “Laptop.” If this computer has no Codex account, another connected account is used instead. Check the provider and model in the chat before sending. If no usable account is connected, finish sign-in before continuing. Explicitly choosing a provider that still needs connection keeps that setup available.
Already-running sessions retain their original account. A fallback does not attach your run to a provider session belonging to another account or computer; the saved conversation history supplies the context for continuation. See models and provider usage.
Understand the sync state
| State | Meaning and next action |
|---|---|
| Offline or pending | Local work may still need upload. Preserve it and reconnect. |
| Locked | Unlock the existing Vault before reading or writing protected records. |
| Syncing | Transfers and version checks are in progress. |
| Synced | Supported records are current for the completed cycle. This is not a full checkout backup. |
| Conflict | Compare the versions and preserve local typing until you deliberately resolve them. |
Workspace content is encrypted; the server also stores nonsecret ownership, relationship and version metadata needed for synchronization and retention. Deletion leaves tombstones so an offline computer can learn that a record was removed. Do not repeatedly recreate old data from a stale copy.
See new messages as they arrive
When another computer saves a change, the server sends a small notice with no message content, and this computer downloads the change itself. If the real-time connection is unavailable, Vortex checks again periodically, so updates can arrive a little later.
| You see on this computer | Meaning |
|---|---|
| New messages in an open chat | The other computer's run is progressing. Earlier pages load when you scroll back to them. |
| Starting, waiting for input or waiting for tasks | The run on the other computer is starting, has a question or approval, or waits for a background or linked task. Answer approvals on the computer running the work. |
| A paused queue with Resume queue | Queued messages received through sync arrive paused. Resume them only if this computer should send them. |
| An empty new chat | A conversation created moments ago on another computer is not in the cloud yet. It fills in once the upload completes. |
Drafts, including their attached files, are not uploaded and are not replaced by another computer's draft. Finish or copy the text on the computer where you wrote it.
Keep active work on its owning computer
A live task lease identifies the device running that work. Reading its synchronized history does not move the process or permit a duplicate simultaneous run. Let it finish or use the explicit ownership controls. Browser tabs, terminal processes and agent execution remain local.
To answer and direct desktop agents from a phone, use Remote pairing. That is an explicit connection to the computer, separate from simply signing in and downloading history.
Protect work during recovery
Do not clear the profile or replace encryption keys to dismiss a sync error. Check the account, Vault, folder binding and local provider selection separately. Keep recoverable profile data and original files intact while investigating an upgrade.
For missing messages, use chat search and recovery. For encrypted access, follow Vault recovery. Read storage and deletion before treating cloud history as a permanent archive.