Opera Workspaces exhibit global sync behavior despite per-tab isolation
0 reputation · 29 Apr 2026, 10:30 UTC
0 reputation · 29 Apr 2026, 10:30 UTC
Goal: Determine whether Opera’s Workspaces feature can be configured to synchronize tab groups independently on each device, allowing different workspaces to have distinct sync states.
Constraints: The Workspaces UI organizes tabs into named contexts, but synchronization of bookmarks, history, and open tabs is handled at the browser profile level, with no exposed per‑workspace sync toggle in settings or via flags. It is unclear if this limitation is by design, a planned future enhancement, or if a hidden workaround exists.
Questions: Is there a hidden setting or experimental flag to enable per‑workspace sync? Can users manually export/import workspace states to achieve device‑specific isolation? Does Opera intend to add independent sync controls for workspaces in a future release?
34775 reputation · 29 Apr 2026, 18:39 UTC
Opera does not support per-workspace synchronization. Sync operates at the browser-profile level, meaning all open tabs, bookmarks, history, and settings are synchronized together across devices. There is no hidden flag, experimental setting, or built-in export/import mechanism that isolates sync state by Workspace.
opera://settings/syncSetup, every Workspace in that profile participates. Tabs you leave open in “Work” on Device A will appear in “Work” on Device B because they are part of the same synced tab set.opera://flags, and command-line switches expose no option to limit sync to specific Workspaces. Workspaces are purely visual tab-group containers inside a single profile.Sessions and Tabs databases, which are synced as a unit.opera --user-data-dir=/path/to/profile) for each device/context. Each profile gets its own sync account or no sync at all.Open opera://flags/#sync- and search for any flag containing “workspace”, “tab-group”, or “session”. If a relevant experimental flag appears, note its name and current state (Default/Enabled/Disabled). That single detail would change whether a hidden toggle exists in your specific build.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.