Getting Started · 02

Get your HQ set up

HQ installed. Now make it yours — import context, wire integrations, create your first skills.

Import your existing work

01

Run /import-claude and point HQ at your existing Claude or Codex projects, repos, or loose files. HQ scans for plans, commands, skills, hooks, policies, knowledge files, and MCP configs — then structures them into your company directory.

HQ is an umbrella for all your context. The more context you migrate, the smarter every session becomes — your AI tools draw from the full picture instead of starting cold each time. Import early, import everything.

HQ / Acme

Imported 14 artifacts

  • 3 skills → companies/acme/skills/
  • 2 policies → companies/acme/policies/
  • 5 knowledge files → companies/acme/knowledge/
  • 4 skills → .claude/skills/

Secrets and API keys are automatically redacted during import.

Local HQ
/import-claude import my project called my-app in Documents
Auto modeOpus 4.8 · High

Test HQ Deploy

02

Deploy a small app to verify your deploy pipeline works end to end. Run /deploy and HQ orchestrates the full flow: build, sensitivity scan, localhost preview, access mode selection, and upload — with guardrails that block oversized or misconfigured deployments.

A test deploy catches config issues early — missing env vars, broken build commands, oversized bundles — before they block real work. Choose an access mode: public (no gate), password-protected, or private (email allowlist).

buildsensitivity scanlocalhost previewaccess modeupload
HQ / Acme

Deploy complete

  • Build: pass
  • Guardrails: 42 files, 1.8 MB gzipped — pass
  • Access mode: password
  • URL: https://acme-app.indigo-hq.com

Access modes: public | password (24h JWT) | private (email allowlist)

Local HQ
/startwork company-name/deploy create a basic hello world web app
Auto modeOpus 4.8 · High

Set up secrets and integrations

03

Use hq secrets to manage API keys, tokens, and credentials. Secrets are stored securely per company and injected automatically when you run commands — no .env files floating around your repo.

Declare what your project needs in .env.schema with hq() markers. When you run hq run, secrets are resolved and injected — no manual wiring.

# .env.schema

STRIPE_SECRET_KEY=hq()

DATABASE_URL=hq()

GITHUB_TOKEN=hq()

HQ / Acme

Secret stored

  • Encrypted and stored per-company
  • Auto-injected via hq run
  • Access controlled by company ACLs
Local HQ
/hq-secrets add my Stripe secret key to Acme
Auto modeOpus 4.8 · High

Create skills and workers

04

Skills are single-responsibility capabilities — a focused task defined in a SKILL.md file and invoked via slash command. Workers are full agents that own multiple skills, have their own identity and knowledge context, and are spawned as separate sessions via /run.

Start with skills for simple automations. Graduate to workers when a domain (design, security, deploy) has enough skills and context to justify a dedicated agent.

Worker

frontend-designerworker.yaml
owns →
ui-reviewSKILL.md
component-genSKILL.md
style-auditSKILL.md

Standalone Skill

/hq-syncSKILL.md
← no workerInvoked directly via slash command

Worker

  • Full agent with identity + context
  • Owns multiple skills
  • Spawned via /run
  • Has its own knowledge pointers

Skill

  • Single-responsibility logic
  • Defined in SKILL.md
  • Invoked via /name
  • Can be standalone or worker-owned

Sync and share

05

Everything you build — knowledge, skills, workers, policies — stays local until you sync. Run /hq-sync to push to the cloud, or hit Sync in the app bar. Share specific files or directories with teammates via /hq-share — it mints an encrypted link that grants them access to the shared vault paths via a browser picker. Build the habit early: sync often, share generously.

Sync

/hq-sync

Bidirectional. Local ↔ cloud. All companies.

Share

/hq-share

Encrypted link. Single-use. 15-minute expiry.

Report feedback

06

Found a bug or have a suggestion? Run /hq-bug from any session. It captures your current context (session state, recent commands, environment) and files a structured report — no manual reproduction steps needed.

HQ / Acme

Feedback submitted

  • Submitted: feedback_a3f8c2e1-9b47-4d6a-bc12-7e5f3a8d9c01
  • Context attached: session state, git status, recent commands
  • Environment: HQ, macOS, Claude Code

Include what you expected vs. what happened for fastest resolution.

Local HQ
/hq-bug sync fails when my knowledge repo has uncommitted changes
Auto modeOpus 4.8 · High
Previous01 · Install HQNext03 · HQ Cloud Concepts