Skip to main content
This page covers running HyperAgent via the Hyperbrowser Cloud API. For using the HyperAgent SDK directly in your own code (local or self-hosted), see the HyperAgent SDK documentation.
HyperAgent is our open-source tool that supercharges Playwright with AI. To view the full details on HyperAgent, check out the HyperAgent Github Repo. Here, we will just go over using one of the features of HyperAgent which is being able to have it automatically execute tasks on your behalf on the web with just a simple call. By default, HyperAgent tasks are handled in an asynchronous manner of first starting the task and then checking its status until it is completed. However, if you don’t want to handle the monitoring yourself, our SDKs provide a simple function that handles the whole flow and returns the data once the task is completed. You can view your HyperAgent tasks in the dashboard.

How It Works

You can use HyperAgent in two ways:
  1. Start and Wait: SDKs provide a startAndWait() method that blocks until the task completes and returns the result
  2. Async Pattern: Start a task, get a job ID, then poll for status and results—useful for long-running tasks or when you want more control

Installation

Quick Start

The simplest way to run a HyperAgent task is with the startAndWait() method, which handles everything for you:

Async Pattern

When you need more control, use the async pattern to start a task and poll for results:

Stop a Running Task

Stop a task before it completes:

Parameters

string
required
Natural language description of what you want HyperAgent to accomplish. Be specific for best results.
string
default:"0.8.0"
Version of HyperAgent to use. Options: 0.8.0, 1.1.0
We highly recommend using the 1.1.0 version of HyperAgent.
string
default:"gpt-4o"
LLM model to use. Available options:
  • "gpt-5.6-luna" - GPT-5.6 Luna
  • "gpt-5.5" - GPT-5.5
  • "gpt-5.2" - GPT-5.2
  • "gpt-5.1" - GPT-5.1
  • "gpt-5" - GPT-5
  • "gpt-5-mini" - GPT-5 Mini
  • "gpt-4o" - GPT-4o (default)
  • "gpt-4o-mini" - GPT-4o Mini
  • "gpt-4.1" - GPT-4.1
  • "gpt-4.1-mini" - GPT-4.1 Mini
  • "claude-sonnet-5" - Claude Sonnet 5
  • "claude-sonnet-4-6" - Claude Sonnet 4.6
  • "claude-sonnet-4-5" - Claude Sonnet 4.5
  • "gemini-3-flash-preview" - Gemini 2.5 Flash
  • "gemini-3-flash-preview" - Gemini 3 Flash Preview
Claude and Gemini models are not supported on the 0.8.0 version of HyperAgent.
number
default:"20"
Maximum number of actions HyperAgent can take (clicks, typing, navigation, etc.). Increase for complex tasks.
string
ID of an existing browser session to reuse. Useful for multi-step workflows that need to maintain the same browser session.
boolean
default:"false"
Keep the browser session alive after task completion.
object
Session configuration (proxy, stealth, captcha solving, etc.). Only applies when creating a new session. If you provide an existing sessionId, these options are ignored.
boolean
default:"false"
Use your own LLM API keys instead of consuming Hyperbrowser credits for LLM calls. You will only be charged for browser usage.
object
API keys for openai, anthropic, and google. Required when useCustomApiKeys is true. Must provide keys based on the LLM you are using.
The agent may not complete the task within the specified maxSteps. If that happens, try increasing the maxSteps parameter.Additionally, the browser session used by the AI Agent will time out based on your team’s default Session Timeout settings or the session’s timeoutMinutes parameter if provided. You can adjust the default Session Timeout in the Settings page.

Reuse Browser Sessions

You can pass in an existing sessionId to the HyperAgent task so that it can execute the task on an existing session. Also, if you want to keep the session open after executing the task, you can supply the keepBrowserOpen parameter.
Always set keepBrowserOpen: true on tasks that you want to reuse the session from. Otherwise, the session will be automatically closed when the task completes.

Using Your Own API Keys

Bring your own LLM API keys to avoid consuming Hyperbrowser credits for LLM calls. You’ll still be charged for browser session usage, but save on token costs.

Session Configuration

Customize the browser session used by HyperAgent with session options.
sessionOptions only applies when creating a new session. If you provide a sessionId, these options are ignored.
Proxies and CAPTCHA solving add latency to page navigation. Only enable them when necessary for your use case.

Best Practices

Be explicit about what you want HyperAgent to do. Instead of “check the website”, say “go to example.com, find the pricing page, and extract the cost of the Enterprise plan”.
Simple tasks need 10-20 steps. Complex multi-page workflows might need 50+ steps. Monitor failed tasks and adjust accordingly.
It is usually better to split up complex tasks into smaller, more manageable ones and execute them as separate agent calls on the same session.