Why do AI agents get stuck in CAPTCHA loops?
A CAPTCHA loop happens when an agent keeps retrying a page that keeps showing a check. Each retry adds more traffic to a page that has already challenged the browser, so the check comes back. Wield does not solve checks. When a site shows one, Wield stops with site_challenge. You solve the check once, in your own tab, and then ask again.
How a loop starts
An agent opens a page in a fresh browser. The site shows a check instead of the content. The agent reads that page as a failed step and tries again. It may reload, run a new search or click the same link. The site shows the check again, and the agent tries again. Each round adds steps and cost.
Why more retries make it worse
Retries add requests to a site that has already challenged the browser. In our runs, one blocked browser-agent run on bahn.de took 675.9 s, about 11 minutes, and produced no result. The Wield recipe for the same train search passed 9 of 9 runs, with a median of 2.1 s.
Wield also limits how far a single run can go. A run stops after 12 steps, 40 requests, 5 MB per response or 60 s. Pacing is set per site.
What Wield does instead: site_challenge
When a site answers with a check instead of data, Wield reports site_challenge. The message means the site's bot protection answered, and Wield itself is working. The extension retries once by itself. It may bring the tab to the front and ask you to click or scroll once.
Wield stops at that point. It does not solve the check, and it does not keep retrying the site.
What you do when it appears
- Open the site in your own browser.
- Use the site once. Search for something, and solve the check if one appears.
- Ask your agent to run the task again.
Some sites, such as bahn.de, only trust a browser after some normal use. If the check returns, repeat the steps. Do not loop a recipe to wait for a result.
Your agent receives site_challenge as the result of the run. The message says the site's bot protection answered instead of the data, and that Wield itself is working. It is a signal to stop and ask you. It is not a reason to keep retrying the same site.
FAQ
Can Wield solve CAPTCHAs for my agent?
No. Wield does not solve checks, and it does not recommend CAPTCHA-solving services. You solve the check in your own tab, then ask again.
Why does my agent keep looping?
Agents often treat a check page as a failed step and retry. The retries add traffic to the site without getting past the check. In our benchmark, ImmoScout24 showed an AWS WAF check to the automated browser, and the run was not retried.
How often do CAPTCHAs appear?
Our benchmark does not measure how often checks appear. It records blocked runs per site. See the benchmark page for the per-site results, dated 7 November 2026 and still preliminary.
Does a recipe retry a check?
The extension retries once by itself. After that, the run stops and reports site_challenge. You decide what to do next.
What should my agent do after site_challenge?
It should tell you that the site showed a check, and ask you to open the site once in your own browser. It should not retry the site in a loop. Wield marks results as website content, and the agent is told never to follow instructions found in them.