# FAQ

**The questions people ask before they read anything else.** For a symptom you are actually hitting, go to [Troubleshooting](/reference/troubleshooting/) instead — this page is about what hlix is, not about what went wrong.

Feature-specific questions live with their feature: [tasks](/running/tasks/#common-questions), [the Coding Workspace](/concepts/coding-workspace/#common-questions), [connecting agents](/guides/connect-agents/#common-questions), and [import](/cli/import/#common-questions).

## Is hlix another coding agent?

hlix is the control plane *over* coding agents, and it ships one of its own — **Hlix** — as the default so you can start without wiring anything up. It orchestrates Claude Code, Codex, and Cursor Agent through exactly the same pipeline, chosen per task.

The product is the layer, not the coder: the roadmap, the triage, the isolation, the review evidence, and the QA are identical whichever harness writes the diff. So bringing the agent your team already trusts costs you nothing, and it is not a downgraded path. [Connect your agents](/guides/connect-agents/) lists exactly which ones run today.

## Do I have to switch tools?

No. hlix plugs into the agents and stack you already run — your repos, your models, your delivery tools. See [Integrations](/integrations/).

## Who owns my code and prompts?

You do. hlix runs work through your own provider keys and your own repos. It orchestrates the work; it doesn't claim ownership of it.

## How does hlix keep agents from breaking client work?

Three ways. First, [triage](/concepts/triage/) — every request is classified on complexity and risk before it becomes work, and the riskiest classifications require a human sign-off before any agent is dispatched. Second, isolation — every project has a durable Coding Workspace, and each task receives its own Git worktree and branch inside it. Third, [review gates](/concepts/review-gates/) — every cycle receives automated QA. Projects are autonomous by default; teams can additionally require human approval on every cycle when their policy calls for it.

## Can agents run in parallel?

Yes. That's the point of the [team model](/concepts/agents/): one orchestrator dispatches many worker agents at once, each isolated, so a project's tasks fan out instead of queuing.

## Is there an audit trail?

Security-sensitive mutations write structured audit events with actor, resource, timestamp, outcome, and request correlation. Compliance-critical mutations commit state and audit event in one database transaction. This supports review and incident investigation without claiming append-only or tamper-evident guarantees that the current data plane does not provide.

## Is hlix for solo developers or teams?

Both work, but it's built for agencies and teams running AI on client work at scale — where orchestration, consistency, and review matter most.

## Can I install the CLI, SDK, or MCP server yet?

Not from a public registry. All three are implemented and tested; what is missing is the verified public distribution. [Current versions](/releases/availability/) is the single page that reports the published state of each package and the gate it still has to pass.

## How do I get access?

<a href={`${import.meta.env.PUBLIC_WEB_URL}/#waitlist`}>Request early access</a>. We're onboarding founding agencies now, with founder-led setup.

## Next steps

[Quickstart: ship your first task](/getting-started/quickstart/)
  [Agents & orchestration](/concepts/agents/)
  [Current versions](/releases/availability/)
  [Troubleshooting](/reference/troubleshooting/)