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

# Installation

> Install Chamber CLI in seconds and submit your first GPU workload

# Installation

<Info>
  The Chamber CLI is currently in early access. Contact [support@usechamber.io](mailto:support@usechamber.io) to get access.
</Info>

## First-Time Setup

<Info>
  **Chamber guides you through everything.** Just run `chamber login` and follow the prompts. No manual configuration required.
</Info>

### Step 1: Login

```bash theme={null}
chamber login
```

This opens your browser to authenticate. After logging in, you're automatically configured.

<Accordion title="Using an API token instead?">
  For CI/CD or headless servers, use token-based auth:

  ```bash theme={null}
  chamber login --token ch.your-api-token
  ```

  Generate tokens in the [Chamber Dashboard](https://app.usechamber.io) under **Settings > API Tokens**.

  <Note>
    The [AI Assistant](/cli/chat) (`chamber chat`) requires browser-based login and does not support API tokens.
  </Note>
</Accordion>

### Step 2: Verify

```bash theme={null}
chamber whoami
```

That's it! You're ready to submit workloads.

## Submit Your First Workload

Navigate to your training code and run:

```bash theme={null}
chamber run ./my-training-project --gpus 4 --team <team-id> --dry-run
```

<Tip>
  **First time?** The `--dry-run` flag shows you exactly what Chamber will generate without actually building or submitting. Remove it when you're ready to run for real.
</Tip>

### What happens next

If it's your first time, Chamber will interactively guide you through:

1. **Registry setup** — Choose Google Artifact Registry, AWS ECR, or another registry
2. **Docker installation** — If Docker isn't installed, Chamber offers to help
3. **Cloud CLI setup** — If AWS CLI or gcloud isn't configured, Chamber walks you through it

```
$ chamber run ./my-project --gpus 4 --team abc123

No container registry configured

Chamber needs a container registry to store your Docker images.

Select your registry type:

  [1] Google Artifact Registry (recommended for GCP users)
  [2] AWS ECR (recommended for AWS users)
  [3] Other Docker registry

Select an option [1]:
```

After the one-time setup, future runs are instant:

```bash theme={null}
# This just works now
chamber run ./my-project --gpus 4 --team abc123
```

## Optional: Set Your Organization

If you belong to multiple organizations, set a default:

```bash theme={null}
chamber config set organization_id your-org-id
```

<Tip>
  Find your organization ID in the [Chamber Dashboard](https://app.usechamber.io) under **Settings > Organization**.
</Tip>

## Shell Completion

Enable tab completion for faster workflows:

<Tabs>
  <Tab title="Bash">
    ```bash theme={null}
    # Add to ~/.bashrc
    source <(chamber completion bash)
    ```
  </Tab>

  <Tab title="Zsh">
    ```bash theme={null}
    # Add to ~/.zshrc
    source <(chamber completion zsh)
    ```
  </Tab>

  <Tab title="Fish">
    ```bash theme={null}
    chamber completion fish | source
    ```
  </Tab>
</Tabs>

## Next Steps

<CardGroup cols={3}>
  <Card title="AI Assistant" icon="message-bot" href="/cli/chat">
    Ask about workloads, capacity, and more
  </Card>

  <Card title="Auto-Containerize" icon="wand-magic-sparkles" href="/cli/run">
    Submit training jobs with `chamber run`
  </Card>

  <Card title="Command Reference" icon="terminal" href="/cli/commands">
    Explore all available commands
  </Card>
</CardGroup>