macOS Agents Window: native reCAPTCHA v2 handling vs My Machines Computer Use?

Support Help
, , ,
1

Hi Cursor team, @deanrie @mohitjain — could you clarify the supported behavior for the local macOS Agents Window, separately from Grok Bot’s hosted browser?

Setup

  • Cursor desktop 3.28.5 on macOS.
  • Browser Automation offers Off or Browser Tab.
  • Cursor CLI: 2026.10.22-27dcf5f.
  • My Machines Computer Use is not enabled on this Mac.

Reported problem
During a Calendly form workflow, the agent reported that the reCAPTCHA v2 Enterprise challenge frame at recaptcha.net/recaptcha/enterprise/bframe did not load and submission returned recaptcha_challenge_failed. The original frame failure has not yet been independently reproduced or traced to a particular network error. The clean scheduling page renders in external Chrome; that does not establish that the challenge works there.

My goal is for the agent to complete the challenge autonomously through a supported native Cursor capability, rather than requiring me to solve it manually.

Questions

  1. Does Cursor currently support autonomous visual completion of reCAPTCHA v2/Enterprise in the local Agents Window, or is human takeover the intended product behavior?
  2. Does My Machines with agent worker --computer-use start and Cursor Computer Use on macOS change that answer, or does it only provide desktop/browser interaction tools?
  3. Can an existing local Agents Window chat use that worker, or must this run as a separate Cloud Agent targeted at My Machines?
  4. Is there a known issue or supported setting for reCAPTCHA challenge frames failing to render inside Browser Tab? Which sanitized console/network details should I collect?
  5. Is there any first-party supported solution for unattended workflows when a third-party site insists on a CAPTCHA? Please distinguish native support from third-party solver MCP integrations.

I reviewed the Computer Use docs, My Machines docs, and Browser docs. I also found the related local CLI orchestration discussion and cloud-browser CAPTCHA report, but not an answer specific to this local macOS Browser Tab case.

Thanks for confirming the intended capability and recommended setup.

5

Hey @Jonathon_Tamm, thanks for laying everything out so clearly!

The built-in browser is designed so that when an agent runs into a CAPTCHA, login wall, or similar check, it stops and hands control back to you instead of retrying. The intended flow is that you clear the check yourself in the Browser Tab and let the agent pick up from there. Since cookies and storage persist per workspace, you usually won’t be prompted again on subsequent runs. These checks exist specifically to stop automation, so a human is expected to pass them.

That holds true for agent worker --computer-use start as well. Running a worker on your Mac gives an agent desktop-level control through the Cursor Computer Use helper app (screenshots, clicks, typing, driving Chrome), but it adds no specific CAPTCHA capability. A simple checkbox may occasionally go through. Image challenges and reCAPTCHA Enterprise scoring are designed to reject synthetic input, so we can’t promise that.

Worth noting too that My Machines is a Cloud Agent target, and an existing local Agents Window chat can’t be moved onto a worker. You’d start a new agent and select your machine under My Machines in the “where the agent runs” picker at cursor.com/agents.

For the challenge frame not loading at all in the Browser Tab: there’s no setting involved, and the Browser Tab doesn’t block third-party frames. More often, the site’s risk check is simply declining an automated session, which can surface as recaptcha_challenge_failed. If you can reproduce it, a few details would help us confirm:

  • whether it also fails when you open the page and click through yourself with no agent driving
  • the status or error on the request to recaptcha.net/recaptcha/enterprise/bframe (the agent can pull the browser’s network and console logs for you)
  • any console errors mentioning CSP, frame-ancestors, X-Frame-Options, or third-party cookies,
  • whether the same page completes in regular Chrome
  • your Cursor version!