> ## Documentation Index > Fetch the complete documentation index at: https://docs.expanse.sh/llms.txt > Use this file to discover all available pages before exploring further. # Quickstart > Install the CLI, register your first compute, and run your first analyse. ## 1. Install the CLI ```bash theme={"dark"} curl -fsSL https://expanse.sh/install | sh ``` Verify: ```bash theme={"dark"} expanse version ``` ## 2. Sign in ```bash theme={"dark"} expanse login --api-key exp_user_… ``` Provide your personal `exp_user_*` API key, created from the Console settings page after you sign in through your organisation's SSO (or set `EXPANSE_API_KEY`). The CLI mints and stores a local session. Confirm it worked: ```bash theme={"dark"} expanse status ``` ## 3. Register a compute A **compute** is anywhere `expanse-daemon` runs: a SLURM cluster, a Nomad cluster, or a Kubernetes cluster. ```bash theme={"dark"} expanse compute register ``` The command asks what kind of compute you're registering and prints the install command or bootstrap snippet to run on the target. Within a minute the compute appears at [console.expanse.sh](https://console.expanse.sh). ## 4. Run a workload Every workload that runs on the compute is captured **automatically**. No change to how anyone submits. ## 5. Predict and diagnose Right-size resources **before** you submit: ```bash theme={"dark"} expanse analyse train.slurm # SLURM batch script expanse analyse train.py # source file ``` Get solution-oriented guidance **after** a failure: ```bash theme={"dark"} expanse diagnose ``` `` is the Expanse execution ID; find it with [`expanse executions`](/cli/overview#expanse-executions) or in the Console. If you only have the scheduler-native ID, pass it with `--source-type`: ```bash theme={"dark"} expanse diagnose 41982 --source-type slurm ``` ## Next steps How Expanse captures evidence and improves its models. What a compute is and what's supported. How analyse and diagnose work. Every command and flag. Personal keys and SSO.