> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mutagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# mutagent helix version, doctor, smoke

> Check which Helix version cloud sandboxes run, and run Helix's own diagnostics and smoke test in a cloud sandbox.

<Note>
  **Early access.** Cloud sessions and managed agent runs are not open to every account yet: we are
  letting accounts in gradually while we test. They run in a cloud sandbox operated by Mutagent, so
  there is nothing to host. A sandbox with nothing to do for 15 minutes stops; send the session a
  message and it wakes up, delivers your message and carries on in the same conversation.
</Note>

Use these commands to check the Helix build that cloud sandboxes run, for example before you report
a problem.

**Before you start:** [install the CLI](/cli/installation) and [sign in](/cli/commands/login)
(`MUTAGENT_API_KEY=<key> mutagent login --json` for a coding agent), and select a workspace with
`mutagent workspaces use <workspace-name>`. `doctor` and `smoke` start a temporary cloud sandbox, so
your account needs cloud sandboxes enabled. `smoke` runs one real model turn, so the workspace needs a
default model: see [mutagent helix models](/cli/commands/helix-models).

## mutagent helix version

Show this CLI's version and the Helix version that cloud sandboxes run. `mutagent helix --version`
prints the same. For the Helix on your machine, run `helix --version`.

```bash theme={null}
mutagent helix version --json
```

```text theme={null}
cli    <cli-version>
helix  <helix-version> (pinned by the image, per the backend’s presets)
```

The Helix version is the one the cloud image is released with, as the server reports it. With
`--json`, the output is `{ cli, helix, helixSource }`.

## mutagent helix doctor

Run Helix's diagnostics in a new cloud sandbox. The sandbox is removed afterwards. The command exits
with Helix's exit status, so a failed check fails the command. It checks the cloud image, not your
machine: for your local Helix, run `helix doctor`.

```bash theme={null}
mutagent helix doctor --json
mutagent helix doctor --strict --json
```

| Flag | What it does |
| - | - |
| `--strict` | Also start Helix's model harness, and fail if it does not start. |
| `--welcome` | Print the Helix welcome screen instead of the report. |
| `--preset <name>` | Start the sandbox from this [preset](/cli/commands/sandbox#mutagent-sandbox-presets). |

With `--json`, the output is `{ success, command, result: { sandboxId, exitCode, stdout, stderr,
timedOut, tornDown } }`. Success is exit code `0` with `result.exitCode` `0`. On a failure, read
`result.stdout` and `result.stderr`; `result.timedOut` is `true` when Helix did not finish in time.
`--refresh-runtime` is refused: the cloud image has no Helix runtime to refresh.

## mutagent helix smoke

Run Helix's smoke test in a new cloud sandbox: one real model turn. The sandbox is removed afterwards.
The command exits with Helix's exit status.

```bash theme={null}
mutagent helix smoke --json
```

With `--json`, the output has the same shape as `mutagent helix doctor --json`.

| Flag | What it does |
| - | - |
| `--preset <name>` | Start the sandbox from this [preset](/cli/commands/sandbox#mutagent-sandbox-presets). |

## mutagent helix update

Not available in the cloud: the command refuses and names the Helix version the cloud image runs.
The release sets that version. To update the Helix on your machine, run `helix update`.

## If it fails

| Exit code or error | Fix |
| - | - |
| `3` (`AUTH_REQUIRED`, `WORKSPACE_REQUIRED`) | [Sign in](/cli/commands/login), then `mutagent workspaces use <workspace-name>`. |
| `2` (`AUTH_EXPIRED`, `INVALID_API_KEY`) | Sign in again, or set a valid `MUTAGENT_API_KEY`. |
| `CLOUD_NOT_ENABLED` (exit 1) | Cloud sandboxes are not enabled for your account yet. Nothing was started. |
| Any other non-zero exit from `doctor` or `smoke` | Helix's own check failed in the sandbox. Read `result.stdout` and `result.stderr`, and include them when you report it with `mutagent feedback send "<what happened>" --category helix`. |

See [CLI errors](/cli/errors) and [Troubleshooting cloud runs](/helix/cloud/troubleshooting).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.