Workspace vs Manual File Management in Neorg for Scaling a Personal Knowledge Base

Direct Answer

Neorg does not synchronize the same .norg file across separate Neovim instances automatically. Each instance owns its own buffer and parser state, so workspace assignment remains consistent only when both instances share the same workspace root and configuration; edits in one instance appear in another only after a reload or explicit sync. After an external edit, :Neorg sync (or a buffer reload) is required to invalidate parser caches and refresh workspace-relative link resolution.

Likely Explanation

Neorg delegates file watching to Neovim and does not maintain a cross-process change feed. Two Neovim processes editing one file therefore maintain independent buffers, and the parser cache in one instance can grow stale while the other instance writes to disk.

Confirmed Facts

• Workspace routing: Workspaces define a root directory and file patterns; links resolve relative to that root, so configuration stability is required for consistent file location.
• Multi-instance editing: Neovim buffers are per-process; opening the same file in two instances creates independent buffers with no built-in locking or cross-instance auto-sync.
• Parser cache: :Neorg sync invalidates and rebuilds the cache; edits made outside Neovim are not detected automatically.
• Version assumption: Recent Neovim with a current Neorg release; older versions may handle buffer events differently.

Steps for This Case

1. Open the same .norg file in both instances using identical workspace configuration.
2. Edit and save in one instance.
3. In the other instance, run :checktime or :e, then :Neorg sync to refresh parser caches and link targets.
4. For edits made outside Neovim, run :Neorg sync after regaining focus to clear stale cache entries.

Scaling Recommendation

Prefer the directory-management workspace for automated file creation and predictable paths, keeping the workspace configuration identical across instances. Manual management offers full control but raises path-mismatch risk as the knowledge base grows. Pair either approach with Git if concurrent edits are expected, because Neorg provides no concurrency control.

Missing Diagnostic Detail

Do you expect concurrent editing of the same files across instances, or only occasional external changes from a single active editor? This determines whether Git conflict handling is needed in addition to cache syncing.