# Context-Switching Tools Need Synced State Not Just Separate Spaces ## Claim A tool that lets you switch between work contexts only reduces friction if the switch carries your configuration with it — otherwise it has relocated the setup cost, not removed it. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds when the underlying tool supports partitioned-but-linked configuration (profiles within one instance) rather than fully separate instances that share nothing. - Breaks when the contexts genuinely need hard isolation — security boundaries between clients, for instance — where synced settings become a liability rather than a convenience. - This is about configuration/state sync specifically, not about whether separate contexts should exist at all. ## Evidence Notebook Navigator 3 introduced vault profiles specifically to solve a named pain: "each individual vault has their own settings for themes and plugins and you can't sync those between the vaults." Before profiles, switching between a work vault and a personal vault meant re-doing theme and plugin configuration by hand in each one — the separation existed, but the switch itself carried a repeated setup tax. ## Links - [[3. Resources/Permanent Notes/Reproducible Environments Encode Repeated Setup as Config]] — extends: the general fix for repeated-setup tax is capturing it as portable config once, not re-doing it per context - [[3. Resources/Permanent Notes/Friction Is the Feature - PKM Tools That Make Synthesis Easier Make Thinking Easier to Skip]] — contrasts: this note argues for removing incidental setup friction, while that note argues some friction (synthesis, not configuration) is worth preserving — the two aren't in tension once "setup" and "thinking" are separated - [[3. Resources/MOCs/Personal Knowledge Management MOC]] — applies-in: multi-vault Obsidian workflows are the direct case this claim generalizes from ## Tests / falsifiers - Compare time-to-productive-work when switching contexts with synced profiles versus fully separate instances with no shared config; if separate instances show no measurable slowdown, the claim is wrong for that tool class. - Check whether users with hard isolation needs (e.g., client-separated vaults) report the sync as a risk rather than a convenience — that would narrow scope rather than falsify the claim. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Full Document Contents/Articles/Mastering Notebook Navigator 3 for Obsidian]] — describes the vault-profiles feature and the settings-duplication problem it responds to.