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

# Secrets and user input

> Provide env-backed secrets and scoped variables to browser-agent runs without putting credentials in prompts.

Do not put credentials, tokens, or private values directly in a browsing goal. Pass secrets as scoped variables.

## CLI secrets

```bash theme={null}
export DEMO_ACCOUNT_EMAIL="person@example.com"

web agent \
  --url https://example.com/login \
  --allow-domain example.com \
  --secret accountEmail=DEMO_ACCOUNT_EMAIL \
  --approval ask \
  "Open the account page and summarize the billing status. Do not change settings."
```

The CLI reads `DEMO_ACCOUNT_EMAIL` from your environment and exposes it as `accountEmail` only to the browser-agent run.

When `--allow-domain` is present, the secret is scoped to that domain. When no domain is present, the CLI scopes secrets to the start URL domain when it can.

## SDK variables

```ts theme={null}
const agent = web.agent({
  model,
  browser: { policy: { allowedDomains: ["example.com"] } },
  approval: "ask",
  variables: {
    accountEmail: {
      value: process.env.DEMO_ACCOUNT_EMAIL ?? "",
      sensitive: true,
      allowedDomains: ["example.com"],
      description: "Demo account email for read-only billing review.",
    },
  },
});
```

Use descriptions to tell the agent what a variable is for. Keep the raw value out of logs, prompts, and final answers.

## Ask for user input

If the workflow needs a human decision, use approvals instead of hiding the decision inside a prompt.

Examples:

* Approve a form submission.
* Confirm a file upload.
* Decide whether a blocker should stop the run.
* Review output before sending it to another system.

<Warning>
  Keep unattended examples read-only. Require explicit user authorization before account changes, purchases, legal acceptances, or destructive operations.
</Warning>