PrompteryxBeta
    ⌘K
    PlatformSupport
    Menu
    IntroductionInstall Desktop & extensionQuick StartPlatform Overview
    OverviewWhat you can makeAI Browser Agent in the chatModels and AutoConnectorsSchedulesProjectsExplore and publishingShare linksMemory and SkillsPersonal agent (beta)Welcome, settings and skinsPlans, credits and top-upsPrompteryx DesktopGroups (pilot)Phone app (early access)
    OverviewCreating WorkflowsTesting & DebuggingScheduling
    OverviewGetting StartedCommandsRecordingSettingsStructured OutputParallel AgentsTips & Best Practices
    OverviewInstallationSidebar AgentUsing Attached FilesExecute on Current TabExporting to Visual Studio
    Overview
    OverviewOpen PageClickClick CoordinatesFillExtract TextScreenshotWaitPress KeyFocus ElementBlur ElementSelect TextHighlight ElementSet ViewportGet Bounding BoxScrollHoverSelect OptionAssertionsCookiesEvaluate JavaScriptExample Workflows
    OverviewPrompteryx Browser AgentOpenAI
    OverviewSchedule TriggerWebhook Trigger
    OverviewGoogle SheetsGoogle CalendarConnect Hub (3,000+ apps)Example Workflows
    AI Vision SettingsChrome Automation ProfilesCloud BrowserBrowser Profiles & Persistent ContextVideo RecordingExecution LogsSharing & CollaborationEdit History
    Selectors GuideVariables
    Start hereGet an API keyRun the AI browser agentDrive a cloud browserRun workflows from anywhereUse connected apps (Connect Hub)SDK (TypeScript)CLIMCP for AI assistants
    REST APIWebhooksMCP toolsCloud Browser APICloud Browser quickstartMigrate from Browserbasen8nZapierMake.com

    Need help? Contact Support

    1. Documentation
    2. Features
    3. Cloud Browser

    Cloud Browser

    Feature

    Run your automations on a cloud-hosted browser without needing a local Chrome installation. Execute workflows from anywhere, use residential proxies, and watch sessions in real-time.

    What is Cloud Browser?

    Cloud Browser allows you to run your Visual Studio workflows on a remote, cloud-hosted browser instance. Instead of opening a local Chrome window, your automation runs on a secure server with a full browser environment. This is useful when you want to:

    • Run automations without a local Chrome installation
    • Use residential proxies to appear as a real user from different countries
    • Keep your login sessions persistent across multiple executions
    • Watch your automation live in real-time from any device
    • Run automations in the background without opening a browser on your machine

    Key Features

    Live View
    Watch your automation running in real-time. A "Watch Live" button appears during execution, opening a viewer window where you can see exactly what the browser is doing. You can also interact with the browser directly if needed.
    Residential Proxies
    Route your browser traffic through residential IP addresses so websites see you as a regular user. Choose from multiple proxy locations worldwide to appear as if you're browsing from a specific country.
    Persistent Sessions
    Keep your cookies, login sessions, and browser state between executions. When enabled, you won't need to log in again each time your automation runs — the cloud browser remembers your sessions.
    Automatic CAPTCHA Solving
    When a workflow hits a reCAPTCHA v2, hCaptcha or Cloudflare Turnstile challenge, the cloud browser can solve it automatically. Solves count against your plan's monthly CAPTCHA allowance, and you can turn this off in the Cloud Browser settings.

    Getting Started

    Every plan includes cloud browser minutes. The free trial includes 10 minutes so you can try it; paid plans (Starter, Developer, Pro and Enterprise) include a monthly allocation of cloud browser minutes and residential proxy data. The residential proxy and video recording aren't available on the free trial.

    1Select a Cloud Profile

    In the Visual Studio toolbar, click on the profile selector dropdown. Below your local Chrome profiles is a Cloud Profiles section listing the Default Cloud Profile and any cloud profiles you've created (use “New Cloud Profile” to add one). Select a cloud profile to use the cloud browser for your next execution. The section header shows the minutes left this month.

    The toolbar profile selector open: the Chrome Profiles section (marked Not connected, with a Set up button) above the Cloud Profiles section with remaining cloud minutes
    The profile selector — Chrome profiles alongside Cloud Browser profiles (shown on the AI Browser Agent; Visual Studio's toolbar has the same selector).

    2Configure Settings (Optional)

    Open the settings panel in Visual Studio (gear icon) and navigate to the "Cloud Browser" tab. Here you can configure the viewport size, session timeout, proxy settings, and more. These settings are saved and apply to all cloud browser executions.

    3Run Your Workflow

    Click "Run Workflow" as usual. The automation will execute on the cloud browser instead of locally. A "Watch Live" button will appear in the Execution Results pane, allowing you to open a live view of the browser session.

    4Open a Standalone Session

    You can also open a cloud browser without running a workflow. In the dropdown, click the Open icon next to any cloud profile. This launches a cloud browser session for that profile that you can use interactively — useful for manually logging into websites to establish sessions that will persist for future automations.

    Settings Reference

    Cloud browser settings can be configured from the Visual Studio settings panel (Cloud Browser tab) or from the general Settings dialog. All settings are saved to your account and apply automatically.

    Default Viewport Size

    Sets the browser window dimensions for cloud sessions. Choose from standard sizes like 1280x720 (HD), 1920x1080 (Full HD), 1440x900, or 1366x768. A larger viewport helps with websites that require more screen space, while smaller viewports can be faster for simple automations.

    Session Timeout

    Maximum duration (in minutes) before a cloud session automatically ends. This prevents forgotten sessions from consuming your monthly minutes. Range: 1 to 360 minutes (6 hours). Default: 10 minutes. The session will close automatically when this timeout is reached, even if a workflow is still running.

    Auto-close After Execution

    When enabled, the cloud browser session automatically ends after your workflow finishes executing. When disabled (the default), the session stays open after execution completes, allowing you to inspect the browser state, continue interacting, or run additional workflows on the same session. Minutes continue to be counted until the session is closed or reaches its session timeout. Scheduled workflows always auto-close, whatever this setting says.

    Persist Browser Context

    When enabled (default), cookies, localStorage, and login sessions are preserved between cloud browser executions. This means if you log into a website during one session, you'll still be logged in on the next session. Disable this if you want each execution to start with a fresh, clean browser state.

    Auto-solve CAPTCHAs

    When enabled (default), reCAPTCHA v2, hCaptcha and Cloudflare Turnstile challenges are solved automatically. Each solve counts against your plan's monthly CAPTCHA allowance (plus any top-up balance). This preference is saved to your account and applies to both cloud and local Chrome executions.

    Enable Residential Proxy

    Off by default. When enabled, your cloud browser traffic is routed through residential IP addresses. This makes your automation appear as regular user traffic rather than datacenter traffic, which helps avoid detection and blocks from websites. Proxy data usage counts towards your monthly proxy data allowance. The proxy isn't available on the free trial.

    Proxy Location

    When the residential proxy is enabled, choose which country's IP addresses to use. Available countries include: United States, United Kingdom, Germany, France, Canada, Australia, Japan, Singapore, India, and Brazil. Websites will see your requests as originating from the selected country.

    Managing Sessions

    Cloud browser sessions can be managed from multiple places in the interface:

    Execution Results Pane

    During and after workflow execution, the Execution Results pane shows a green "Cloud Active" indicator, a "Watch Live" button to open the live viewer, and an "End Session" button to close the session when execution is not running.

    Profile Selector

    When a cloud session is active outside of workflow execution (opened via the Open button), "Watch" and "End" buttons appear next to the profile selector in the toolbar.

    Live Viewer Window

    The live viewer popup window includes an "End Session" button in its header bar. Closing the viewer window does not end the session — use End Session (here or in the Execution Results pane / toolbar) so it stops using your minutes.

    The Cloud Platform's Cloud Sessions page: session ID search, status and recording filters, page-size selector and the sessions table
    Every cloud session also lands in Cloud Platform → Cloud Sessions — searchable by session ID, filterable by status and recording, with replays where available.
    Tip
    If a popup window is blocked by your browser, you can still see active sessions and end them from the Execution Results pane or the toolbar area. Check your browser's popup blocker settings if the live viewer doesn't open.

    Usage & Billing

    Cloud browser usage is measured in two ways:

    Browser Minutes

    Each cloud browser session uses minutes from your monthly allocation. Time is counted from when the session starts until it ends (via auto-close, manual close, or timeout). The minimum charge is 1 minute per session. You can view your remaining minutes on the Subscription page or in the Cloud Browser settings panel.

    Proxy Data

    When the residential proxy is enabled, data transferred through the proxy is measured and counted towards your monthly proxy data allowance. This includes all page loads, images, scripts, and API calls made during the session. Monitor your proxy data usage on the Subscription page.

    Best Practices

    Use Persistent Context for Login-Required Sites
    Enable "Persist Browser Context" when automating websites that require login. Open a standalone cloud session first, manually log in, then close the session. Your login will be remembered for subsequent automated executions.
    Set Appropriate Timeouts
    Set the session timeout to match your expected workflow duration plus a small buffer. For a workflow that runs for 5 minutes, a 10-15 minute timeout is appropriate. This prevents wasting minutes if you forget to close a session.
    Choose the Right Proxy Location
    Select a proxy location that matches the target website's expected user base. For example, if automating a US-based e-commerce site, use a US proxy location. This reduces the chance of geo-blocking or captcha challenges.
    Only Enable the Proxy When Needed
    The residential proxy is off by default. If you're automating internal tools or websites that don't check IP addresses, leave it off to save on your proxy data allowance. The cloud browser works perfectly without a proxy — it just uses a datacenter IP instead.

    Screenshots & PDFs

    You can capture screenshots and generate PDFs using the cloud browser, just like with a local browser profile. However, there are important differences in how files are handled.

    Screenshots

    Full-page and element screenshots are captured in the cloud and returned in the node's output. After execution, open the node's output and go to the Files tab, which shows a preview with “Open in new tab” and Download buttons. Click Download to save the file to your computer.

    PDFs

    PDFs generated with the "Generate PDF" node are captured in the cloud and returned in the node's output. After execution, the node's Files tab shows the PDF with “Open in new tab” and Download buttons. Click Download to save the PDF to your computer.

    Cloud Files Are Temporary
    Screenshots and PDFs generated by the cloud browser are only available during your current session. They are not permanently stored on our servers or in the cloud. Once you navigate away from the execution results or start a new execution, the files will no longer be available. Make sure to download any files you need immediately after the workflow finishes. For local browser profiles, files are saved directly to your computer's Captures folder and persist permanently.

    Related Documentation

    Chrome Automation Profiles

    Learn how to manage local and cloud Chrome profiles for your automations.

    Visual Studio Overview

    Learn about the Visual Studio workflow builder where cloud browser is used.