Skip to content

Current versions

The current published version of each hlix package, and how to install it. Every version on this page is rendered from the release ledger, so it always matches what the registry serves.

The hlix command: import a project, keep it in sync, and inspect projects and tasks from a terminal.

Install

Terminal window
npm install --global @hlix/cli
hlix --version

In CI, and anywhere the toolchain must not change underneath you, pin the version instead of floating to latest:

Terminal window
npm install --global @hlix/cli@0.2.0

Start at Install the CLI, then Authenticate. The full command surface is in the CLI reference.

The first-party TypeScript client: authentication, retries, typed errors, uploads, and SSE streaming against the same contract the CLI uses.

Install

Terminal window
npm install @hlix/sdk

Pin the version in CI so a build never picks up a client you have not tested against:

Terminal window
npm install @hlix/sdk@0.2.0

See the TypeScript SDK for client creation, the error classes, and the retry policy. To generate a client in another language, use the OpenAPI contract directly.

The official MCP server: it exposes workspace-scoped projects, tasks, cycles, comments, and review evidence to Cursor, Claude Code, Codex, and Windsurf.

Configure your client

Your MCP client launches the server itself — there is nothing to install by hand. The version is pinned so a client restart cannot silently upgrade a server holding your workspace credentials.

Save as .cursor/mcp.json in the project.

{
"mcpServers": {
"hlix": {
"command": "npx",
"args": [
"-y",
"@hlix/mcp@0.2.0"
]
}
}
}

Connect a client

  1. Authenticate once with the CLI.
    Terminal window
    hlix auth login --workspace <workspace-id>

    The server reuses the owner-only credential written by the CLI. Never paste an API key into an MCP config or command argument.

  2. Bind the repository by importing it.
    Terminal window
    cd /path/to/project
    hlix import .

    hlix init selects the API and workspace but does not create or bind a cloud project. A successful import writes the project ID used for strict project scoping.

  3. Use the version-pinned configuration above.

    Restart the client or begin a new agent session, then inspect its MCP server list. A user-level global configuration can omit a local binding and operate across the selected workspace.

  4. Run a read-only check.

    Ask the agent to list Hlix projects or read one task. In a bound repository, the server exposes only that project and rejects cross-project IDs.

See the official MCP server for the tool list, the write gate, and per-client notes.

Terminal window
hlix --version
npm view @hlix/cli version

Expected result: two version numbers. When they differ, the installed CLI is older than the registry’s current release — upgrade with the install command above, or pin deliberately.

  • hlix --version disagrees with npm view. You have an older global install. Re-run the install command, then open a new shell so PATH resolves the new binary.
  • npm error E404 on a version you see here. Check for a typo in the package name; @hlix/cli, @hlix/sdk, and @hlix/mcp are the only three.
  • An MCP client keeps starting an old server. The configuration pins a version. Update the pin in the client config and restart the client — the server does not self-upgrade, deliberately.
  • A generated API client is missing an endpoint. It is missing from the published contract, so no client can reach it. See what the contract does not cover.