Troubleshooting setup and sync
Recover from missing commands, wrong-company context, invite confusion, and sync conflicts without making the problem worse.

Recovery ladder
Stop, identify the layer, recover the correct state, then continue.

Find the failing layer
Most failures belong to install, local setup, company selection, sync, invite, /startwork, permissions, or context overload.
Write down what you expected, what command you ran, what company name is visible, and whether the session has gotten long or confused.
Recover setup
Setup recovery repairs the local HQ foundation before company work resumes.
Re-run setup repair, install missing prerequisites, then confirm HQ opens from the intended workspace and profile.


Recover sync
Sync recovery protects shared state, company isolation, and trust in HQ.
Stop edits, verify the company name, resolve conflicts, and rerun sync before /startwork.
Keep the chapter executable.
Repairs or completes local HQ setup when install or workspace state is incomplete.
Refreshes company state and surfaces conflicts that must be resolved before work continues.
Confirms the recovered setup can load the intended company context.
What to keep in mind.
Recovery order
Install, setup, company, sync, invite, then /startwork. Fix the earliest broken layer first.
Stop condition
Wrong company name, duplicate company prompt, or unresolved sync conflict means stop before editing.
