Skip to main content
Grok Computer Use allows Grok 4.5 to directly interact with a browser to perform tasks much like a human. This capability lets Grok move the cursor, click buttons, type text, and navigate the web, automating complex, multi-step workflows. Hyperbrowser makes it simple to run Grok Computer Use tasks in managed cloud browsers. Start a task with a single API call, then poll for results or use our SDK’s blocking methods that handle everything automatically. You can view your Grok Computer Use tasks in the dashboard.

How It Works

You can use Grok Computer Use 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 Grok Computer Use 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 Grok to accomplish. Be specific for best results.
string
default:"grok-4.5"
Grok model to use. The only supported option is "grok-4.5".
string
default:"medium"
Reasoning effort for Grok. Available options:
  • "low"
  • "medium"
  • "high"
number
default:"50"
Maximum number of actions Grok can take (clicks, typing, navigation, etc.). Increase for complex tasks.
number
default:"3"
Maximum consecutive failures before the task is aborted.
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.
boolean
default:"true"
Allow the agent to interact by executing actions on the actual computer, not just within the page. Allows the agent to see the entire screen instead of just the page contents.
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 xAI API key instead of consuming Hyperbrowser credits for LLM calls. You will only be charged for browser usage.
object
API key for xai. Required when useCustomApiKeys is true.
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.
useComputerAction can often be better for completing tasks but may require more steps. It is especially useful when the agent needs to interact with elements on the page that might not be accessible by or visible to Playwright. Since it allows the agent to see and interact with the entire screen, it is much more powerful. Instead of executing actions with Playwright which can only interact with the page via CDP, computer actions allow the agent to interact directly with computer primitives (direct clicks, typing, scroll, etc.).

Reuse Browser Sessions

You can pass in an existing sessionId to the Grok Computer Use 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 xAI API key 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 Grok Computer Use 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 Grok 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.