The outcome

Complete a permitted multi-step browser task while keeping credentials, navigation, and side effects under review.

Step by step

A workflow you can repeat.

  1. 01

    Define the exact sites, task, allowed interactions, prohibited actions, login policy, session lifetime, and evidence required for completion.

  2. 02

    Connect the hosted MCP server with OAuth or a least-privilege token kept outside chat, URLs, screenshots, logs, and source control.

  3. 03

    Start with a public read-only task, inspect each snapshot and planned action, and require confirmation before forms, downloads, messages, or purchases.

  4. 04

    For authenticated work, enter credentials through an approved human handoff, limit session state, and never expose secrets in model-visible page text.

  5. 05

    Verify the result independently, save only necessary evidence, close the browser session, revoke temporary access, and record failures for retesting.

Working standard

What good use looks like.

  • Allowlist sites and actions.
  • Keep credentials out of model context.
  • Require approval before side effects.

Official references

Check the current product documentation.