Skip to content
Indigo HQ Docs

Roadmap Overview

Current Status

HQ has shipped. It now runs as a split ecosystem of independently versioned repos (see the Ecosystem & Repo Map), installed end-to-end via npx create-hq and synced through the cloud engine and the menubar app.

ProductStatus
hq-core (npx create-hq scaffold)✅ Shipped — hqVersion 15.x
@indigoai-us/hq-cli✅ Shipped — the hq CLI (5.x)
@indigoai-us/hq-cloud✅ Shipped — bidirectional S3 sync engine
hq-sync (menubar app)✅ Shipped — Tauri 2 desktop app with auto-update
hq-console (admin UI)✅ Shipped — Next.js admin surface
hq-deploy (artifact platform)✅ Shipped — subdomain hosting + deploy API
hq-pro (vault + teams)✅ Shipped — vault, identity, team platform
hq-packages (content packs)✅ Shipped — hq install @indigoai-us/hq-pack-*
Documentation✅ Live on Vercel

Forward Priorities

The launch checklist is done. Priorities now are per-product depth and the surfaces that are newest:

  1. Desktop sync polish (hq-sync) — conflict-resolution UX, richer per-file progress, broader platform coverage.
  2. Team platform depth (hq-pro + hq-console) — membership management, usage visibility, and admin workflows.
  3. Deploy platform hardening (hq-deploy) — SSR flows, custom domains, enterprise init.
  4. Content-pack ecosystem (hq-packages) — more first-party packs and a smoother authoring/install loop.
  5. Capability coverage (hq-secrets, hq-share) — documentation and ergonomics for the CLI capability surfaces.

Effort is sized by scope and risk, not by calendar dates. HQ runs at agent velocity with many concurrent sessions, so “how long” is better expressed as sessions of work than weeks.

How to Read This Section