Collaboration is not syncing

Use this when two signed-in people expect to see the same vault state, cursor presence, or document updates through KB-1 Cloud.

Local-only daemon mode does not provide Cloud collaboration. In local-only mode, verify the local daemon and files instead.

Check membership first

A user can only enter an organization’s vaults if they are a member of that organization. Ask an admin to open Organizations, expand the org, open Members, and confirm the affected account appears in the member list.

If the user was just added, have them sign out and sign back in before testing again.

Confirm both people are in the same place

Compare these fields:

Same organization slug.
Same vault slug.
Same note path.
Same hosting mode: self-hosted relay or Hosted.

A stale browser tab can look like a sync issue when it is actually pointed at an older org, different vault, or moved note path.

Self-hosted checks

On the daemon machine, run:

curl -fsS http://127.0.0.1:7382/api/health
curl -fsS http://127.0.0.1:7382/api/relay/status
curl -fsS http://127.0.0.1:7382/api/vaults

The relay status should show relay.configured: true and relay.controlConnected: true. If it is not, use The daemon is running but Cloud shows it offline.

Hosted checks

For Hosted orgs, open the Hosted status diagnostic while signed in:

/api/orgs/<org-slug>/hosted/status

If the status shows a wake, restore, or sync-agent failure, wait for the current wake attempt to finish once. Repeated failures should be treated as a Hosted runtime issue, not a user editing problem.

Check whether edits reached disk

For daemon-owned vaults, flush the vault and then read the file from disk:

curl -fsS -X POST http://127.0.0.1:7382/api/vaults/<vault-id>/ops/flush

If the file is correct on disk but another browser is stale, refresh the stale browser. If the file is not correct on disk, investigate save warnings and daemon logs before asking users to continue editing.