Cross-Device Synchronization

Telemus AI can keep supported workspace content available across linked devices through a configured sync hub. A connection to a hub confirms connectivity; check sync status separately to confirm that your changes were received and applied.

What synchronizes

Supported workspace content includes mind maps, workspace settings and layouts, eligible saved notes and artifacts, and supported shared shapes. Availability also depends on the app version, device and configured hub.

Ordinary workspace sync does not transfer everything in an installation. Private assistant history, channel conversations, provider credentials, running processes, and every local file or imported model are not automatically shared. A successful room sync is not proof that conversation history or full project context moved to another device.

Keep participating devices updated. Older apps can reject newer content or retain an earlier version. After an update, let each device complete a normal sync before using cross-device editing.

Connect and check status

Use Networking Center in the native app, Network → Sync in Command Center, or /networking in the terminal to inspect the current connection. Check the selected workspace and hub before enabling live sync.

• Enable live sync starts automatic updates to the configured destination.
• Pause live sync stops automatic updates while keeping connection settings.
• Sync now requests a transfer; its status determines whether it completed.
• Main hub last applied in Web, or Last primary apply in the terminal, shows when incoming content was last successfully applied. An unset value is not a successful sync.
• A connected hub, recent heartbeat or successful sign-in alone does not prove that the workspace has arrived on another device.

When the hub is unavailable, keep your local work and inspect status before changing settings. Do not clear application data, relink repeatedly or resend an uncertain operation to dismiss an error.

License checks and saved hubs

Routine license checks and credential refreshes for the same account and device keep saved sync hubs. Sync status can be temporarily unavailable during verification; this does not grant offline access.

Signing out, switching accounts, unlinking a device or confirmed license revocation clears the old account's sync binding. An expired Command Center browser session is separate from the app's account/device link.

A saved pause remains in effect after restart, backgrounding and routine account refresh. Resume explicitly when ready. Joining or configuring a connection, or an explicit account setting that enables sync, can change that state. Read the result before assuming that sync is still paused.

Keep the active workspace separate from hub mirrors

A secondary hub does not select its workspace as your active workspace. Check both the active workspace and the intended hub when using more than one hub.

If status says sync heartbeat workspace did not match the active configuration, pause live sync and ask the operator to review the identities. Avoid scene edits during that review. Do not relink, rename the remote workspace, or press Sync now simply to clear the notice.

Saving changed connection settings is not a recovery procedure and may resume sync. Preserve existing data and credentials until the intended workspace has been confirmed. Installing a newer app does not restore data already lost in an earlier incident.

Hosted Web world access

On a configured hosted deployment, Load VR World (Web) opens a scene view using your authenticated Command Center session. The host checks access before showing data. Viewing this hosted scene does not make the browser a separately licensed device or copy the host's credentials into it.

The hosted view can show the selected hub's saved mind map, supported shared shapes, eligible notes as read-only panels, and a limited set of models loaded on the host. A model visible here may be host-only; visibility does not establish that it was saved to the hub or downloaded by another device. Local-only, archived and conflicted notes are excluded. A notice identifies content that cannot be displayed.

The hosted scene has different capabilities from the other browser surfaces:

Surface	What to expect
Standalone Web 3D	A browser-owned workspace with its own account, providers, files and saved state. Browser storage and platform limits apply.
Hosted Web world	A limited scene view and session-owned chat. Supported mind-map edits are described below; it is not a complete mirror of the host's tools, panels or history.
Command Center	The authenticated host dashboard for task, memory, session and operational controls. Its panels are separate from the browser's 3D world.

Opening Command Center from the world does not transfer a private hosted chat or grant another tool permission. Hosted models, shapes and notes remain read-only where editing controls are unavailable. Where hosted transform controls are available, supported models can be moved and uniformly resized. General export retrieval is not currently offered. Web is flat-only; it is not a Web XR target.

A brief refresh or server delay can keep the current scene visible. Persistent access failure shows a recovery notice. Logout, session expiry or confirmed access loss clears the hosted view. The view does not overwrite your standalone browser workspace or turn on the host's automatic sync.

Move a node and save it

Grab a mind-map node, drag it, then release. Wait for the save result before moving another node. The change applies to that node in the selected saved hub; it does not publish the whole browser world.

Saved means the accepted position was checked with the hub. If the map changed since it loaded, reload the snapshot before trying again. When a save cannot be confirmed, check the refreshed map. An uncertain write is not automatically repeated, and closing the view cannot undo a write the hub already accepted.

Double-click a node, or double-tap it on a touch screen, to edit its label and colour where supported. These edits follow the same save rules. Annotation and link editing and node deletion remain unavailable in this hosted editor.

Other devices receive saved changes through their own sync. They must have current access and a compatible app version. Simultaneous edits can conflict; check the receiving device before assuming the same view is present everywhere.

Independent browser sync

Independent sync requires the browser's own account/device sign-in, license and workspace permission. A hosted session can provide access to a configured sync connection without exposing its server credential, but it does not replace the browser's own authorization.

To link the browser, open Account → Link this device in Web 3D and approve its code through the normal account page. Command Center also provides Device sync → Sync this browser guidance. Relinking the Command Center host is a separate operation.

A visible background, successful login or server-side object count does not prove that the browser has received the map. Check browser storage, account and sync status while preserving the saved world.

Recover a mind map to one saved hub

An operator can use authenticated POST /api/networking/sync-now, or pass the same JSON after /networking sync-now in the terminal, for a selected-hub mind-map recovery.

1. Select an existing hub_id and the current workspace_id.
2. Set content to mind_map and begin with action: "probe".
3. Use the returned request_id with action: "status" to read the result.
4. Only after a ready probe, use action: "publish" with that exact request_id and confirm: true.
5. Check status again. Only verified confirms the post-publication check.

Do not include credentials or a server URL in the request. This copies only the selected mind map, not every room object or every hub. Existing remote content, conflicts, incomplete responses and capacity limits can stop recovery.

Keep automatic sync paused during reviewed recovery if appropriate. A pause does not block all local editing or undo completed changes. If the result is outcome_unknown, preserve the receipt and ask the operator to inspect the outcome before another probe or publish. Do not repeat an uncertain publication.

The normal Web and in-world Sync now buttons are unchanged. This recovery is an operator API/terminal workflow, not a new spatial recovery wizard.

Models and large artifacts

Model availability depends on the deployed app and hub. A hosted display model is not necessarily a shared model. Where static-model transfer is enabled, self-contained GLB files are limited to 32 MiB; unsupported compression, animation, external texture dependencies or decode limits can prevent transfer.

Supported Web receivers display models read-only. Web does not publish or upload models through this sync workflow. A failed download keeps the previously visible model, and reloading the browser can require another download. The hub and current access must remain available.

Publishing a model or saving its pose requires its own supported, confirmed workflow. It must not be inferred from moving a local model while sync is paused. A received status can precede downloading and rendering, so inspect the receiving device separately. Windows private-cache support and persistent browser model caching are not generally available through this workflow.

Eligible saved artifacts can be up to 256 KiB each, subject to overall transfer limits. Larger or unsupported content produces a failure or remains at an older version on an older peer. This is not unlimited history synchronization.

Private, local-only and redacted records are excluded from ordinary artifact transfer. Their exclusion cannot be bypassed by displaying them as a note. Use normal archive or delete controls; directly removing stored data is not a supported way to send a deletion to other devices.

If a device reports Shared 3D objects deferred, other eligible workspace content may still sync while those objects remain unchanged. See shared-object limits. Do not delete models or recovery records to bypass a capacity or identity error.

Sync history and conflict review

The native Workspace Sync view, Web Network → Sync and terminal /networking show recent sync activity. Open Conflict Review in native, Review conflicts in Web, or run /networking conflicts in the terminal.

These are bounded status views, not a complete transfer ledger. Old snapshots are marked stale. A failed read is not an empty conflict list. A dismissed conflict is not proof that a change was delivered or that remote data was undone.

Web and terminal conflict views omit synced values. Native owner-local review can show retained private values and offer supported manual recovery. Use that review deliberately; clearing a notice does not resolve every data difference.

Opening a large hosted workspace

A large workspace can take time to validate and restore. Command Center shows Workspace is starting while normal data and action requests are unavailable. Previously loaded conversations can remain visible during a temporary failure. Do not treat an unavailable list as an empty workspace.

The Web world launcher stays disabled until a usable hub is available. No active sync hubs. Check Network settings. means the host has no current launch target. A storage-startup error is not a reason to relink your account.

If the separate banner This Command Center needs to be re-linked to your Telemus account appears, use Relink device and finish the normal account consent flow. This repairs the host's account link, not independent browser sync. It does not resume a saved sync pause.

Mobile throttling

Quest and Android can reduce or pause automatic sync under thermal or low-battery pressure. Local changes remain available for a later successful transfer. Allow time for the receiving device to catch up before judging a handoff complete.

Handoff and export

Use supported export-pack tools to share selected notes, tasks and summaries with someone who does not use Telemus AI. Check the saved file location reported by your device. An export is a separate, read-only handoff; it does not keep another person's copy synchronized or revoke copies already delivered.

Related guides

• Connectivity and Collaboration
• Continuity and Recovery
• Platform Support