# Documentation

Install the Composal CLI and verify your product with browser agents, acceptance journeys, and recorded evidence.

## Start with a user journey

Composal Verify uses browser agents to test user journeys, check expected outcomes, and record evidence you can replay. Test a staging, preview, or production URL, or use a managed shadow environment. You can run tests manually or on a schedule without connecting a repository.

1. [Install the CLI and sign in](/docs/quickstart).
2. [Prepare a project environment and saved Scenarios](/docs/verify#first-run).
3. Launch a run and review its assertions, browser replay, and findings.

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

The macOS and Linux installer needs no `sudo` and configures your shell’s PATH. Open a new terminal if prompted, then run `com login`.

## Verify your product

- Define actions and expected outcomes in plain English. Use personas to test different user roles.
- Trace each run's evidence to the ready environment revision and saved Scenario definitions it used.
- Run tests manually or on a cron schedule. Repository-backed runs can select journeys based on a Change.
- Watch browser agents as they work, then review recorded steps, screenshots, video, and Console and Network events.
- Investigate reproducible failures. Verify remembers navigation lessons across runs; assertions determine the result.
- Plan, launch, and inspect hosted runs from your terminal or connected agent using the CLI or MCP.

Start with [Verify overview](/docs/verify), learn [how the browser agent runs](/docs/verify/agent), or use the [scenario and MCP reference](/docs/verification) for credentials, Expectations as Code, and evidence controls.

## Supporting workflows

### Follow a testing guide

- [Test a GitHub pull request preview](/docs/verify/guides/github-previews) before merging a change.
- [Test an authenticated user journey](/docs/verify/guides/authenticated-journeys) with dedicated accounts and role-specific outcomes.
- [Test a private preview or internal app](/docs/verify/guides/private-apps) through your VPN or firewall allowlist.

### Agents and automation

[Set up agents](/docs/agents) with verifier skills and MCP tools. Use [scheduled verification](/docs/cli#verify-administration) to keep checking agreed journeys.

### VCS settings

The Source workspace is available in the Vex organization's feature rollout. Open **Source → VCS settings** to manage product activation, repository connection defaults, and Home repository self-review. Create a repository to start with an empty Git history, or connect GitHub or GitLab to import existing source into a standalone repository. Choose **Nodes** within VCS settings to configure GitHub Actions runners, runner pools, and self-hosted CI nodes. Organization administrators can change these settings.

### Deploy and operate

- [GitHub Actions runners](/docs/github-actions-runners): standard tools, VM and sandbox labels, and custom Docker images through Vex.
- [Turborepo cache](/docs/turborepo-cache): persist build artifacts between managed runner jobs and restore matching task outputs over localhost.
- [Hosting](/docs/hosting) covers apps, services, deployments, domains, CDN, and static sites for your verification targets.
- [Composal registry](/docs/registry) covers organization-scoped container images.
- [Remote builders](/docs/remote-builders) describes Docker build support and its current availability.
- [Managed OpenTelemetry](/docs/managed-otel) connects logs, metrics, and traces to application investigation.

## Reference

- [Verifier CLI reference](/docs/cli): environments, project Scenarios, grouped runs, findings and evidence.
- [CLI configuration](/docs/cli-configuration): sign-in, organization context, and local settings.
- [CLI changelog](/docs/cli/changelog): versioned command-line release notes.
- [API reference](/docs/api): the generated public API contract.