Skip to content
Indigo HQ Docs

Ecosystem & Repo Map

HQ is a set of independently versioned repos that compose through published npm packages, GitHub Releases, and one shared AWS Cognito identity. Each repo ships on its own cadence. A CLI release does not require a desktop app release, and the cloud apps deploy independently of the scaffold.

The repos at a glance

RepoShips asWhat it is
hq-coreGitHub releases (tarball)The scaffold for an HQ instance: skills, policies, scripts, and runtime config for Claude Code (.claude/), Codex (.codex/), and Grok (.grok/), plus a Cursor rules file (.cursor/rules/hq.mdc). Changes land in hq-core-staging first.
create-hqnpx create-hqThe terminal installer. Downloads the hq-core scaffold, checks dependencies, and offers hq-cli and the recommended packs.
hq-cli@indigoai-us/hq-cliThe hq CLI: sign-in, packs, cloud sync, files, secrets, DMs, integrations, bots, and diagnostics.
hq-cloud@indigoai-us/hq-cloudThe sync engine behind the CLI and the desktop app. Ships the hq-sync-runner binary.
hq-desktop-appmacOS and Windows app (GitHub Releases)Tauri 2 app that runs onboarding on first launch, then syncs in the background and hosts the desktop workspace. Replaces the earlier hq-sync, hq-sync-win, and hq-installer apps.
hq-consoleNext.js app (hq.computer)Web console for companies, teams, files, deploys, and usage.
hq-deployAWS data planeServes deployed web artifacts on subdomains; deploy-management API.
hq-proSST app on AWSThe vault, team platform, VaultApi (hqapi.hq.computer), and shared Cognito identity.
hq-packagesContent packs (packages/hq-pack-*)Optional packs installed into an HQ instance with hq install.

Each product has a dedicated page under Products.

How they compose

Composition rules

  • The scaffold seeds an instance. create-hq (or the desktop app’s onboarding) lays down hq-core once. Later core updates come from new hq-core releases, applied with /update-hq or hq rescue, not through a shared package dependency.
  • The CLI owns sync commands; the engine does the work. hq-cli depends on @indigoai-us/hq-cloud and loads it only when a sync command runs. hq-cloud also ships hq-sync-runner, which emits ndjson sync events.
  • The desktop app is a GUI over the same engine. hq-desktop-app spawns hq-sync-runner and renders its progress. See hq-sync and hq-cloud.
  • One identity, many apps. hq-pro provisions the shared Cognito pool and the vault. hq-console authenticates against it (NextAuth/OIDC) and hq-deploy trusts JWTs minted by it. Neither has its own user store.
  • Capabilities install as packs. Optional add-ons (design styles, Slack bots, and others) live in hq-packages. hq-core’s core/core.yaml lists the recommended packs by GitHub source, for example hq install github:indigoai-us/hq-packages#packages/hq-pack-design-styles. See hq-packages.

Versioning

Each repo carries and releases its own version:

RepoCurrent versionRelease mechanism
hq-corehqVersion 16.0.x (core/core.yaml)hq-core-staging → promote-to-hq-core workflow opens a release: v<ver> PR on hq-core; merging it tags and cuts the release
create-hq10.xPush a v* tag; CI publishes to npm
hq-cli@indigoai-us/hq-cli 5.xPush a v* tag; CI publishes to npm with OIDC trusted publishing
hq-cloud@indigoai-us/hq-cloud 6.xPush a v* tag; CI publishes to npm
hq-desktop-app0.11.x (versions.toml)v* tag → signed macOS and Windows builds plus updater manifests on GitHub Releases
hq-console / hq-deploy / hq-proper-repoVercel (hq-console) and AWS deploys
hq-packagesper-pack version in package.yamlrelease.yml on push to main publishes changed packs to npm

Older package metadata may still point repository.url at the archived combined repo. The split repos above are canonical.

Where to go next