Skip to main content

​
Roadmap

Where HQ is headed. For what’s already shipped, see the feature tour and changelog.

​
v0.2 — Connectors & Hardening

The gateway runtime and workspace foundations are solid after v0.2.0–v0.2.2. The remaining v0.2 work focuses on expanding the connector layer and closing the last polish gaps.
  • Source connector expansion — Google Drive, Gmail, and improvements to the connector SDK to make community contributions frictionless.
  • Test coverage hardening — expand UI component coverage and add end-to-end install validation across platforms (VPS, M-series Mac, Raspberry Pi).
  • Task recurrence — enable the recurrence system (built but currently disabled) with schedule presets and UI controls.
  • Templates source UI — let workspaces point at a custom git URL for their own template library instead of only the bundled set.
  • Import existing OpenClaw — bring an existing OpenClaw setup into HQ without starting over. Detect running agents, import their state, and register the host as an HQ gateway.

​
Next — Deeper Autonomy

Make agents meaningfully more capable and less dependent on human routing.
  • Deeper OpenClaw integration — channel hand-off (agent moves between Telegram → browser → Slack mid-task), richer browser automation, tighter lifecycle hooks.
  • Agent-to-agent workflows — define multi-agent coordination patterns so agents can chain work without human dispatch.
  • More channels — WhatsApp and Signal support for agent communication.
  • Per-agent desktop view — pause, takeover, and resume individual agents from the desktop modal, not just the whole gateway.
  • Pretty tailnet URLs — Tailscale Serve automation in the installer for clean http://hq access instead of ported URLs.
  • Plugin ecosystem growth — more built-in plugins beyond usage-alerts and better webhook plugin DX.
  • Dev agent — a built-in agent that can modify HQ itself — UI components, templates, configuration, workflows — so operators can customize their workspace through conversation instead of code.

​
Future — Runtime Freedom

Remove hard dependencies and give operators real choices.
  • Hermes runtime support — Hermes as an alternative agent runtime alongside OpenClaw. Requires a runtime abstraction layer in the gateway so operators can choose their execution engine.
  • Supabase Local / Pure Postgres — remove the Supabase dependency for self-hosters who want plain Postgres, making HQ deployable with just a database connection string.
  • Community template marketplace — discover, share, and fork agent templates across the community.
  • Native apps — macOS menu bar, iOS Shortcuts.
  • Stronger per-agent isolation — stricter security boundaries for multi-operator deployments.

​
Shipped

Items that graduated from the roadmap into a release.

​
v0.2.2 (June 2026)

  • Subtask UI — task detail modal with inline subtask create, status toggle, progress bar, and parent breadcrumb navigation. Board and list views show subtask progress chips.
  • Knowledge library scope — knowledge items can now be scoped to library for workspace-wide shared context.
  • E2B keepalive enhancements — sandbox health-check and renewal logic with pause/resume functionality.
  • Dispatcher hardening — burst-aware batch sizing, inbox dedup, backoff for unprovisioned agents. Prevents wake-loop resource exhaustion on small instances.

​
v0.2.1 (June 2026)

  • Gateway backup & restore — gateway state automatically backed up to Supabase Storage on shutdown and restored on fresh boot. Manual trigger from Settings → Backups.
  • Backups settings page — per-gateway backup status, on-demand backup, and delete action with real-time updates.
  • OpenClaw 6.6 runtime — gateway upgraded from 6.1 to 6.6 with entrypoint hardening and backup/restore lifecycle.

​
v0.2.0 (June 2026)

  • OpenClaw 6.1 gateway runtime — gateway, dispatcher, and runner images upgraded from 4.12 to 6.1.
  • MiniMax M3 model — added to the model picker (1M-token context, multimodal, low cost).
  • Full new-workspace wizard — “Add Workspace” now has parity with initial onboarding, one-click DB migration, and multi-workspace auth.
  • Gateway verification harness — automated boot-and-assert test for the full agent loop on sandbox.
  • Onboarding polish — first-run experience stabilized across all install paths (auth propagation, gateway credential resolution, login redirects).

​
How to Influence the Roadmap

  • Open issues labeled feature-request with a clear use case.
  • Start discussions in github.com/yourhq/yourhq/discussions.
  • Send PRs for docs, templates, UI polish, gateway hardening, or well-scoped integrations.
  • For large architecture changes, open an issue first so the design can be discussed before implementation.