# 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.

## `@hlix/cli`

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

```bash
npm install --global @hlix/cli
hlix --version
```

Run it once without installing:

```bash
npx @hlix/cli --help
```

In CI, pin the version instead of floating to `latest`:

```bash
npm install --global @hlix/cli@0.2.0
```

Start at [Install the CLI](/getting-started/install/), then [Authenticate](/getting-started/authentication/). The full command surface is in the [CLI reference](/reference/cli/).

## `@hlix/sdk`

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

```bash
npm install @hlix/sdk
```

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

```bash
npm install @hlix/sdk@0.2.0
```

See the [TypeScript SDK](/sdk/typescript/) for client creation, the error classes, and the retry policy. To generate a client in another language, use the [OpenAPI contract](/api/openapi/) directly.

## `@hlix/mcp`

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

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.

Cursor (`.cursor/mcp.json`), Claude Code (`.mcp.json`), and Windsurf (`~/.codeium/windsurf/mcp_config.json`) use:

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

Codex uses `.codex/config.toml` in a trusted project or the user config:

```toml
[mcp_servers.hlix]
command = "npx"
args = ["-y", "@hlix/mcp@0.2.0"]
default_tools_approval_mode = "writes"
```

Authenticate with `hlix auth login --workspace <workspace-id>`. Run `hlix import .` to create and bind the cloud project; `hlix init` alone does not write a project ID.

See the [official MCP server](/mcp/) for the tool list, the write gate, and per-client notes.

## Check what you have

```bash
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.
**Pin in CI:** Floating to `latest` means a build can pick up a version you have not tested against. Pin the exact version in CI and upgrade on purpose. [Versions & releases](/releases/versioning/) covers how the version numbers relate to each other.

## If a version looks wrong

- **`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](/api/reference/#what-is-not-here).

## Next steps

[Install the CLI](/getting-started/install/)
  [Versions & releases](/releases/versioning/)
  [Changelog](/releases/changelog/)
  [Quickstart](/getting-started/quickstart/)