Getting Started

Install HQ

01

Head to install.getindigo.ai and download the installer. Pick a folder for your HQ, create your account, and set up your first company. While you wait, the installer runs dependency installs in parallel and sets up the Sync app.

1Welcome
2Install
3Templates
4Prerequisites
5Sign In
6Workspace
7Personalize
8Verify
9HQ Sync
10Done

Set up HQ

Pick a folder, create your account, set up your first company. Dependencies install in parallel while you configure.

Get Started

Open the Sync app

02

Once installed, open the Sync app with the keyboard shortcut below. This keeps your local HQ in sync with the cloud — files, knowledge, and session state travel with you across devices.

+Shift+H
HQ
HQ~/Documents/HQ
Sync
Last syncednever
  • Personal personalLast sync · never
    PERSONAL
  • Acme CorpLast sync · never
    PENDING
  • IndigoLast sync · never
    PENDING
☼ Settings↪ Sign out

Open HQ in your AI tool

03

Open your HQ folder in Claude Code or Codex. Run /setup to finish initial configuration — it wires up commands, verifies dependencies, and prepares your workspace.

HQ / Acme

Setup complete

  • Commands verified (17 slash commands)
  • Workers loaded (26 workers)
  • Knowledge indexed
  • Workspace ready
Local HQ main | worktree
/setup
Auto modeOpus 4.7 · High

Open a new session

04

Start a fresh session in your AI tool. Each session is a clean context window — no accumulated noise from prior work.

Start work

05

Run /startwork [company-slug] to begin.

This resolves your company context, loads policies, surfaces available worker routes, and persists session metadata. It's how HQ knows what you're working on and what tools are available.

HQ / Acme

Session started

  • Company: Acme Corp
  • Policies: 4 company, 2 repo (1 hard)
  • Workers: 8 available
  • Active project: acme-dashboard — 3/7 stories done

Ready to work. Pick a story or describe what you need.

Local HQ main | worktree
/startwork acmeHelp me create a new skill
Auto modeOpus 4.7 · High

Create your first file

06

Create a knowledge file or skill — if you're not sure where to start, a knowledge file is a good default. This is where your team's context lives: decisions, architecture, specs, playbooks.

HQ / Acme

Created knowledge file

  • companies/acme/knowledge/engineering/api-patterns.md
  • Indexed in qmd collection

Knowledge files are available to every session automatically.

Local HQ main | worktree
create a knowledge file for our API patterns
Auto modeOpus 4.7 · High

Push to cloud

07

Sync your work using /hq-sync, or just tell your AI to sync. You can also click Sync in the app bar (top-right corner of the Sync app).

HQ
HQ~/Documents/HQ
Sync
Last syncedjust now
  • Personal personalLast sync · just now
    PERSONAL
  • Acme CorpLast sync · just now
    SYNCED
  • IndigoLast sync · just now
    SYNCED
☼ Settings↪ Sign out

Share with your team

08

Run /hq-share or tell your AI to share. This mints an encrypted share link your teammates can use to pull the files into their own HQ.

HQ / Acme

Share link created

  • Encrypted single-use link minted
  • 3 files bundled
  • Link expires in 15 minutes

Send the link to your teammate — they redeem it in their own HQ.

Local HQ main | worktree
/hq-share companies/acme/knowledge
Auto modeOpus 4.7 · High

End with a handoff

09

Run /handoff when you're done.

Handoff preserves your session state, regenerates indexes, and writes a thread file so the next session picks up exactly where you left off. No context lost between sessions.

HQ / Acme

Handoff complete

  • Thread T-20260519 written
  • 3 files committed
  • Indexes regenerated
  • Next session will resume automatically
Local HQ main | worktree
/handoff
Auto modeOpus 4.7 · High

Commands cheat sheet

10

Bookmark the Operator Cheat Sheet — every command, slash pattern, and worker shortcut on one page.

/startwork/handoff/hq-sync/hq-share/plan/run/learn/setup