Skip to main content

​
Authentication and Profiles

​
Ask for an Authenticated Workflow

Name the Profile and the outcome you need:

​
Named Profiles

Profiles are browser identities and authentication boundaries. Sessions are browser windows or workspaces within a Profile; separate Sessions let multiple agents use the same Profile without sharing navigation state. Use named Profiles when work and personal accounts, customers, or environments must stay separate. When SLAB is the local runtime, a Session may create its own browser window or explicitly bind an existing human window. browser tabs discovers unbound windows without changing them, and binding one tab claims the complete containing window. Normal Session close detaches an adopted human window rather than closing it. Discovery IDs are live-runtime identities; list again after a browser or daemon restart.

​
Hosted Profiles

Webcmd Cloud scopes every hosted Profile to a workspace. The CLI resolves the workspace once per invocation: --workspace <id>, then the WEBCMD_WORKSPACE environment variable, then an implicit default. Within that workspace, --profile <name> selects a browser identity. For an individual user, the implicit workspace and default Profile are created lazily when a hosted browser task first needs them. For a product serving multiple users, set WEBCMD_WORKSPACE per invocation so each user has isolated Profiles and browser state.
Hosted profile list returns Profiles for the active workspace. Delete a hosted Profile only by its immutable ID:
Deletion permanently removes that hosted browser state and its saved sign-in state.

​
When You Need to Sign In

Complete sign-in directly in the browser; never share credentials through chat. The handoff belongs to the Session that started it. After signing in, run the returned verification command verbatim because it includes the Session selector when needed. Webcmd blocks session close while that Session has a live handoff.

​
Credential Safety

Credentials never belong in prompts or retained sitemap memory. Ask the agent to use an authenticated Profile and pause for a browser handoff instead of sharing passwords, cookies, API keys, recovery codes, or one-time codes.

​
Local and Hosted Authentication

In local mode, Webcmd opens or foregrounds the relevant browser Session when human authentication is required. Complete sign-in there, tell the agent when you are done, and let it run the returned verification command before continuing. Hosted browser tasks return a Webcmd-owned live authentication view when interactive sign-in is required. Complete the sign-in there before the agent continues.