Local or Cloud
Choose a Mode
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
- Create an account at
https://api.webcmd.dev/account/signup. - Create and copy an API key from the account page.
- Run
webcmd setup, choose hosted mode, and paste the key when prompted.
--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.
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.
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.