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

# Local or Cloud

> Choose where Webcmd runs and configure the Webcmd Cloud alpha when hosted browser infrastructure is useful.

# Local or Cloud

## Choose a Mode

| Choose local when                                                                       | Choose Cloud alpha when                                                                  |
| --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| The task needs desktop apps, local tools, local adapters, or a browser on this machine. | You want Webcmd to run supported commands and browser sessions on hosted infrastructure. |

The CLI grammar remains the same in either mode.

## Local Mode

Local mode runs Webcmd against this machine's tools, adapters, and browser. Choose it for desktop workflows or work that depends on local state.

## Webcmd Cloud Alpha

Webcmd Cloud alpha is for supported commands and browser sessions on hosted infrastructure. Hosted browser sessions run through Webcmd Cloud's Browser Use-backed infrastructure for browser lifecycle, proxying, and live viewport access.

## Set Up Hosted Mode

1. Create an account at `https://api.webcmd.dev/account/signup`.
2. Create and copy an API key from the account page.
3. Run `webcmd setup`, choose hosted mode, and paste the key when prompted.

Hosted browser tasks are scoped to a workspace. Set `--workspace <id>` or the `WEBCMD_WORKSPACE` env var per invocation (flag wins, then env, then an implicit default workspace); the CLI sends it as the `X-Webcmd-Workspace` header. Within a workspace, `--profile <name>` selects a persona; an omitted selector or `--profile default` lazily creates that workspace's own `default` profile.

```bash theme={null}
# Each downstream user gets their own workspace and its own lazy profiles.
WEBCMD_WORKSPACE=user_64256 webcmd github whoami
WEBCMD_WORKSPACE=user_64256 webcmd --profile work github whoami
```

`webcmd profile list` returns profile rows scoped to the ambient workspace. `webcmd profile delete <profile-id>` permanently removes hosted browser state. When sign-in is required, Webcmd returns a Webcmd-owned live authentication view; complete sign-in there, then let the agent continue. See [Authentication and Profiles](/docs/authentication-and-profiles).

View hosted usage on the account page.

## What Stays Separate

Local and hosted profiles, adapters, site memory, and traces do not sync. Treat each mode as its own working environment.

Local mode has no workspace concept. Local profile behavior is unchanged: an arbitrary `--profile <name>` lazily creates separate local browser state. Local `webcmd profile list`, `rename`, and `use` continue to manage that local state; they do not create or manage hosted profiles.

## Current Boundaries

Cloud is alpha. Billing is not presented as generally available; use hosted mode when its supported infrastructure fits the workflow.