Skip to guide
IndigoIndigo · HQ Field Guide
Chapter 14 / 15Contents
Chapter 14shared · 14 min

Troubleshooting setup and sync

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

01Diagnose setup and sync issues by identifying which layer is failing.
02Use safe recovery paths that avoid wrong-company edits and duplicate companies.
$ /setup
Fig 14.0 · The recovery ladder
The concept

Recovery ladder

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

RECOVERY LADDERFIND THE BROKEN LAYER — RECOVER FROM THERESTARTWORKSYNCCOMPANYINSTALLL4 · SESSIONL3 · STATEL2 · CONTEXTL1 · BASEBROKE HERECOMPANYRECOVEREDCLIMBDOWNTHENUPISOLATE THE FAILING LAYER · REPAIR · RE-CLIMB EACH RUNG TO VERIFY
Fig 14.1 · Find the failing layer
Step 01Layer label

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.

The recovery action targets one layer instead of trying unrelated commands.
/setup/hq-sync/startwork
Step 02Repair

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.

You can run the next company command without missing-command or repeated-setup errors.
npx create-hq/setup
Fig 14.2 · Recover setup
Fig 14.3 · Recover sync
Step 03Conflict clear

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.

You can run /startwork and see the expected company context.
/hq-sync/startwork
Commands

Keep the chapter executable.

Repair setup
$ /setup

Repairs or completes local HQ setup when install or workspace state is incomplete.

Recover sync
$ /hq-sync

Refreshes company state and surfaces conflicts that must be resolved before work continues.

Context proof
$ /startwork

Confirms the recovered setup can load the intended company context.

References

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.

Next
Next move

Finish by turning the first week into a predictable operating rhythm.

Continue to first week
Part 14 · Troubleshooting setup and syncIndigo · HQ Field Guide