Browse AI Robot Stuck on a CAPTCHA: What to Do

If a Browse AI robot stops at a CAPTCHA, first check whether it is stuck while you create or retrain it in Robot Studio, or during an execution task. Browse AI’s CAPTCHA-solving feature is available during execution, not robot creation. For a supported CAPTCHA during execution, ask Browse AI support to enable Solve CAPTCHA for the specific robot; the feature requires a paid plan. If training is stuck, retry and then use the Browse AI Chrome Extension if Robot Studio remains stuck.

1. Identify where the robot stopped

The stage determines the next step:

Robot Studio training or retraining: Solve CAPTCHA is not available in this stage. Retry the training. If it continues to hang or request a retry, train or retrain with the Browse AI Chrome Extension.
Execution task: identify the challenge type. If it is reCAPTCHA or hCAPTCHA, ask Browse AI support to enable Solve CAPTCHA for that robot. This capability is for execution and paid plans.
No visible challenge: check for a changed page layout, expired login session, different loading behavior, or a temporary issue on the target site before assuming a CAPTCHA is the cause.

Record the robot name, task stage, target page, when the failure began, and what the task shows at the stopping point. Those details help support distinguish a CAPTCHA from a changed page or session.

2. Check which CAPTCHA the site uses

Browse AI lists these challenge types as supported by its Solve CAPTCHA feature, once support enables it for the robot:

Challenge	Clues	Documented status
reCAPTCHA v2	Often an “I’m not a robot” checkbox; Google reCAPTCHA branding or resources from `google.com/recaptcha` and `gstatic.com/recaptcha`.	Supported when enabled.
reCAPTCHA v3	Typically runs in the background rather than showing a checkbox.	Supported when enabled.
reCAPTCHA Enterprise	Google reCAPTCHA branding or related resources may be present.	Supported when enabled.
hCAPTCHA	May show an “I am human” checkbox, hCAPTCHA branding, or resources from `hcaptcha.com`.	Supported when enabled.
FunCaptcha	May have Arkose Labs or FunCaptcha branding; technical clues can include `funcaptcha` or `arkoselabs`.	Listed as unsupported.
Text, math, or custom CAPTCHA	Distorted characters, arithmetic prompts, or a site-specific challenge.	Listed as unsupported.

A challenge’s appearance and page resources are clues, not a definitive diagnosis. If the type is unclear, include a screenshot or description when you contact support. Do not assume that enabling the feature will handle an unsupported or custom challenge.

3. Request Solve CAPTCHA for an execution task

Confirm that the task reaches a CAPTCHA during execution, rather than stopping in Robot Studio.
Identify the challenge type from its branding and behavior.
Contact Browse AI support and ask them to enable Solve CAPTCHA for the affected robot or robots.
Include the robot name, challenge type, target page, and a description of what happens during the task.
After support confirms the configuration, run a test task and inspect the result before scheduling or scaling the workflow.

Browse AI says its CAPTCHA feature must be enabled by its support team and is available only on paid plans. Its documented supported set is reCAPTCHA v2, v3, Enterprise, and hCAPTCHA. FunCaptcha, text, math, and custom CAPTCHAs are listed as unsupported. Ask support about an uncertain case rather than assuming a different challenge is covered.

4. If the problem is in Robot Studio

Robot Studio creation and retraining are separate from CAPTCHA handling during execution. If the page presents a challenge while you are trying to teach the robot, Solve CAPTCHA will not resolve that training step.

Retry the training step once, following the prompt in Robot Studio.
If it remains stuck or repeatedly asks you to retry, use the Browse AI Chrome Extension to train or retrain the robot.
Run a test task after training and confirm the robot reaches the intended page and captures the expected data.
If the extension does not resolve the issue, contact support with the robot name, stage, page, and observed behavior.

5. Rule out other common causes

A robot that stops can have a problem other than a CAPTCHA. Check these causes before changing the robot or repeatedly rerunning tasks:

Possible cause	What to check	Next action
Website structure changed	Page layout, labels, or HTML elements no longer match what the robot learned.	Retrain a custom robot, then run a test task.
Expired login session	The page redirects to sign-in, shows a session warning, or no longer displays account content.	Update the robot’s session cookies in its Settings page and test again.
Loading behavior changed	Content now appears later, after lazy loading, or through AJAX.	Inspect the current page and retrain or adjust the robot to match the changed flow.
Temporary target-site issue	The target page is unavailable or behaving inconsistently.	Retry after the site recovers and verify the page manually.
Stronger bot detection	The site blocks automated access, particularly on high-security or login-protected pages.	Check Browse AI’s compatibility guidance and ask support whether the site is supported. Do not assume repeated retries will remove the restriction.

Browse AI’s compatibility guidance says some sites use bot detection its platform cannot overcome, especially high-security sites that require login. It also lists MFA/2FA as unsupported. Test a robot thoroughly before scaling it, and monitor task frequency so the target site is not overwhelmed or more likely to trigger its security measures.

6. Know when to escalate

Prebuilt robot: Browse AI directs users to contact support when one fails.
Custom robot: retrain after a structure change and test it. Contact support if it still fails, if you need to retrain it more than once a month, or if you are unsure how to make it more resilient.
Unsupported or unclear CAPTCHA: give support the challenge type and details. The published guide lists FunCaptcha, text, math, and custom challenges as unsupported.
Persistent high-security block: ask whether the site is compatible. A CAPTCHA feature does not imply that all bot checks, MFA, or access restrictions can be bypassed.

7. Troubleshooting checklist

Symptom	Likely explanation	Action
Robot hangs during creation or retraining	Execution CAPTCHA handling does not apply in Robot Studio.	Retry, then train or retrain with the Chrome Extension.
Execution stops at reCAPTCHA or hCAPTCHA	Solve CAPTCHA may not be enabled for this robot.	Ask support to enable it; paid plan required. Test after confirmation.
Execution stops at FunCaptcha, text, math, or a custom challenge	The challenge is outside Browse AI’s documented supported types.	Contact support to discuss the specific case; do not assume it can be solved.
Robot reaches sign-in instead of the expected content	Session cookies may have expired.	Refresh the session cookies in robot Settings and run a test task.
Robot selects the wrong content or cannot find fields	The website structure or content loading behavior may have changed.	Retrain the custom robot and test against the current page.
Robot fails intermittently on a protected site	Temporary site issues or stronger bot detection may be involved.	Check the page manually, test cautiously, and ask Browse AI support about compatibility.

8. Reduce repeat failures

Test after every retraining or cookie refresh before resuming a scheduled workflow.
Recheck the robot when the target page changes its layout or loading sequence.
Keep task frequency appropriate for the target site’s behavior and monitor failures.
For login-protected pages, watch for session expiry and remember that MFA/2FA is listed as unsupported.
Do not treat a successful test on one page or one run as proof that every challenge type or protected page will work.

Or skip the browser setup

If your goal is to capture a page as an image or PDF rather than extract its structured data with a robot, ScreenshotNeo is a website screenshot API and MCP server. It is an alternative to try first for screenshot capture: cookie and consent banners, newsletter popups, and chat widgets are removed before the shot, and only clean shots are billed. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing; response headers report the page verdict and billing status. Screenshot capture does not solve a CAPTCHA or provide Browse AI-style data extraction.

One GET request returns an image or PDF. See the ScreenshotNeo API documentation for parameters and formats.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', bytes));

Cookie banners, popups, and chat widgets are removed before capture; each cleanup step can be turned off.
Bot checks, blank pages, and failed loads are never billed, and the response identifies the page verdict and billing status.
An MCP server gives Claude, Cursor, and other MCP clients the tools take_screenshot, get_page_info, and capture_pdf.
The free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 screenshots; every feature is on every plan.

FAQ

Does Solve CAPTCHA work while I create a robot?

No. Browse AI documents it for execution, not Robot Studio creation. Retry a stuck training step, then use the Chrome Extension if needed.

Can I enable CAPTCHA solving myself?

Browse AI says its support team must enable the feature for specified robots. It is available only on paid plans.

Does Browse AI support every CAPTCHA?

No. Its guide lists reCAPTCHA v2, v3, Enterprise, and hCAPTCHA as supported when enabled. It lists FunCaptcha, text, math, and custom challenges as unsupported.

Will refreshing cookies fix a CAPTCHA?

It addresses expired login sessions, which can look like a robot failure. Refresh cookies when the robot is no longer authenticated; it is not a general CAPTCHA-solving step.

What if the target site uses MFA?

Browse AI’s compatibility guidance lists MFA/2FA as unsupported. Ask support about the site’s compatibility before relying on a robot for that workflow.