Shared context
Company knowledge, decisions, meeting notes, and policies load into every session — so agents start informed, not cold.
HQ is the shared context layer over Claude Code, Cursor, and Codex — knowledge, skills, secrets, and workflows that stay in sync across your team.
Works where your agents already work
Product
Multi-company by design. Each tenant keeps its own knowledge, policies, credentials, and workers — isolated and searchable.
Company knowledge, decisions, meeting notes, and policies load into every session — so agents start informed, not cold.
Slash commands and specialized workers for plan, review, deploy, CRM, creative, and ops — orchestrated, not ad-hoc.
ACL-backed files and keyless secret bindings. Agents get access when granted — never pasted into chat.
Bidirectional HQ Sync keeps machines and teammates aligned. Local-first root, cloud when you need it.
From brainstorm → PRD → execute → review → land. Deploy previews and gated shares in one flow.
Cross-company knowledge or credential bleed is a category-1 bug. Boundaries are non-negotiable.
How it works
HQ sits on your machine as a structured workspace. Agents read the charter, load company context, and run the same commands your team does.
Scaffold HQ locally. Core ships the system; personal and company layers hold your overlay and tenants.
Knowledge, policies, workers, and vault grants — isolated per company. Invite teammates when you're ready.
Open Claude Code, Cursor, or Codex inside HQ. /startwork resolves context; skills take it from there.
Push state across machines, share vault paths, deploy artifacts, and keep decisions searchable for the next session.
Stack
Local root. Cloud identity. Deploy, vault, and secrets as first-class services — not glue scripts.
“Not another chatbot. A shared operating layer so every agent session starts with the same company brain.”HQ · AI operating system by Indigo
Install the root, onboard a company, and give every agent the same context your best operator has.