# Install the CLI

Install the Composal CLI on macOS, Linux, or Windows with WSL. Sign in, choose your organization, and prepare your first hosted browser verification run.

## 1. Install the CLI

Install Composal on macOS or Linux as your normal user. No `sudo` is needed.

On Windows, run the Linux CLI inside a WSL2 Linux distribution. Open its Linux terminal and run the commands below there. Keep your CLI configuration and project files in the WSL filesystem. Running agent setup inside WSL configures agents in that Linux environment; it does not configure a Windows desktop app.

```sh
curl -fsSL https://dl.composal.com/install.sh | sh
```

The executable is `com`. Composal installs into `~/.composal/bin` and configures PATH for Bash, Zsh, and Fish automatically. Open a new terminal if prompted, then check the installation:

```sh
com --version
com verify --help
```

Verify runs browsers remotely; you do not need a local browser installation to launch a hosted run.

## 2. Sign in

`com login` opens browser authorization and saves your local profile to `~/.config/composal/config.toml`. Confirm the active identity:

```sh
com login
com whoami
```

On a headless machine, use `com login --no-browser` and complete the printed verification URL elsewhere. To use a personal token, use the prompted `com login --token` flow so it does not land in shell history.

For Google or GitHub sign-in, choose the email from your invitation. If you see **No Account Found**, try another account or choose **Request Access**. Signing in with an uninvited email does not create an account.

## 3. Choose an organization

You need Verify enabled for your organization and administrator access to configure targets or launch runs. Choose a default organization, or pass `--org <org>` to verifier commands:

```sh
com context switch <org>
com verify environments list --org <org> --json
com verify admin scenarios list --org <org> --project <project> --json
```

To invite teammates, open **Settings → Organizations**, choose your organization, then open **Team**. Owners and admins can manage member roles and send, copy, resend, or revoke invitations on the same page. Admins can switch teammates between Member and Admin; only owners can assign or change the Owner role. Other members can view the member list.

## 4. Prepare a Verify run

A run needs a ready environment revision and saved project Scenarios. Register an accessible HTTP(S) URL or prepare a managed shadow, define your user journeys and expected outcomes, and store test-account values in your project's **Credentials**.

Follow [Start a run](/docs/verify#first-run) for the dashboard path. The [verifier CLI reference](/docs/cli) walks through registering a URL, importing scenarios, reviewing a plan, and launching browser agents. For a manual run against an existing URL, you do not need to clone or import a repository.

## Next steps

- [Verify overview](/docs/verify) explains triggers and results.
- [Scenario and MCP reference](/docs/verification) covers Scenarios, credentials, recordings, and connected agents.
- [Set up agents](/docs/agents) adds verifier workflow guidance to your coding harness.
- [CLI configuration](/docs/cli-configuration) explains profiles and organization context.