Deep research · 25 September 2026

Why the Cloudflare checkbox fails in AI browsers

You're a real person clicking "Verify you are human," and it still loops. This explains why, what we saw on gameuidatabase.com, and the legitimate ways through. It deliberately leaves out tricks for fooling bot detection.

Not the clickThe checkbox isn't what gets tested
30 minDefault pass length once you're through
2 of 2Site pages that loaded in the pane on 25 Sep
11 botsNamed in the site's ban list, Claude and ChatGPT included

The short answer

Cloudflare doesn't decide from your click. It decides from what it learns about the browser: how it's built, whether something is controlling it, and the reputation of your internet connection. Cloudflare's own docs say remote-controlled browsers are "not supported" for solving its challenges. So the Claude Code browser pane can fail no matter how human the person clicking is.

The good oneOpen the site in your normal Chrome and tick the box there. It works because that's a normal browser with your history and cookies. Claude can then read that tab through the Claude in Chrome extension. When Claude hits a challenge there, it pauses and hands it to you, which is how it's designed to work.

The bad onegameuidatabase.com's owner has told AI agents to stay out. The site's robots file bans 11 named bots, including Claude and ChatGPT. When a request said it was ClaudeBot or ChatGPT, Cloudflare answered with a challenge. A browser that says it's plain Chrome got straight through. There's a history behind that: in 2024 OpenAI's crawler hammered the site for two weeks. Expect AI-driven visits to keep hitting walls there, and don't expect an allowlist if you ask.

Our own tests

What happened on gameuidatabase.com, 25 September 2026

TestResultWhat it means
Opened the homepage and the "Title Screen" category in the Claude Code browser paneLoadedNo challenge on either pageThe challenge doesn't fire every time. The pane isn't banned outright.
Looked at the cookies the pane already holds for the siteA Cloudflare challenge cookie (cf_chl_rc_ni) was already there, from your earlier visitsCloudflare did challenge this browser before. Whether you were let in later is unknown: the pass cookie is hidden from page scripts.
How the pane describes itself to websitesIts browser name includes Claude/2.9939.2. Its brand list shows "Chromium" but not "Google Chrome." The standard "I'm being automated" flag is off.The pane swaps its real "Electron" name for "Claude." Two other apps, T3 Code and Orca, proved that any rewritten name like this makes Cloudflare's check loop with error 600010. That this is the pane's cause is our inference, not proven.
Read the site's robots fileBlocks anthropic-ai, Claude-Web, ChatGPT-User, GPTBot, OAI-SearchBot, Google-Extended, CCbot, Amazonbot, FacebookBot, PiplBot, PetalBotThe owner has chosen not to allow AI access.
Four plain page requests, each claiming a different identityNormal Chrome and the pane's identity got through. ClaudeBot and ChatGPT-User got "too many requests" plus a Cloudflare challenge.CaveatThe two blocked requests came last in a quick burst, so a speed limit may explain it. A safety check blocked the re-run in a different order, so this one isn't settled.
External

Why a human click can still fail

1. The box is a formality

Cloudflare's check runs hidden tests in the background: small puzzles for the computer to solve, probes of what the browser can do, checks for browser quirks, and a learning model. It picks the checkbox or a silent check based on "visitor risk level." It can mark a finished check invalid if it spots bot-like signals. A newer system, called Precursor and launched 13 July 2026, watches mouse, typing and focus for the whole visit, and can cancel a pass midway.

Cloudflare Turnstile docs; Cloudflare blog, 2022-09-28 and 2026-07-13. High confidence.

2. Remote-controlled browsers aren't supported

Cloudflare says browsers driven by automation tools such as Selenium, Puppeteer, Playwright and Cypress "are not supported for solving production challenges." Browsers built into other apps "may have limited functionality." Cloudflare's own hosted browser "will always be identified as a bot." When it sees "strong bot signals," the check loops. That loop is what you saw.

Cloudflare supported-browsers and troubleshooting pages, 2026-08-18 and 2026-09-08. High confidence.

3. A browser that lies about itself fails

Cloudflare says changing the browser's identity during a visit makes the check fail. Another company's app browser, Orca, hit the same wall and published the fix on 5 September 2026. Their browser claimed to be plain Chrome but didn't send the extra details real Chrome sends, so it "reads as a spoof." Their fix was to go back to the browser's honest name and stop leaving the remote-control connection open all the time. T3 Code found the same thing on 12 September 2026: even just dropping the word "Electron" from the name broke the check. The Claude pane does exactly that.

Cloudflare mobile-implementation docs; github.com/stablyai/orca pull 18749; github.com/pingdotgg/t3code pull 7110. High confidence for those apps; inferred for the Claude pane.

4. Your connection counts too

Cloudflare's own fix list says to turn off VPNs and proxies and try another network. One Claude Code bug report, from 4 September 2026, shows Chrome and the Claude desktop app looping on a cloud-server IP address while Safari passed on the same one. Cloudflare doesn't publish how much the address matters.

Cloudflare challenge-solve troubleshooting; github.com/anthropics/claude-code issue 92094. Medium confidence.

5. You can't carry a pass over

Passing gives you a cookie called cf_clearance. Cloudflare says it's "securely tied to the specific visitor and device it was issued to, preventing reuse across machines." It lasts as long as the site sets: 30 minutes by default, and 15 to 45 minutes is recommended. Passing in Chrome doesn't carry over to the Claude pane, or the other way round. Cloudflare doesn't say exactly what the cookie is tied to.

Cloudflare clearance, cookies and Challenge Passage docs. High confidence on the quote, low on what it's tied to.

6. On Windows the pane can crash

At least six Claude Code bug reports say that opening a Cloudflare-checked page in the desktop pane on Windows crashes the whole app. Users traced it to a Windows security rule that blocks a graphics file Cloudflare's check loads. The main report was marked fixed on 15 September 2026 with no explanation. You're on Windows 11. Today's visit didn't crash, but no challenge appeared either.

github.com/anthropics/claude-code issues 80444, 81341, 90461, 90732. High confidence on the trigger; the fix is unconfirmed.

External

How each AI browser handles the checkbox

BrowserUses your real browser?What happens at a challengeProves who it is to sites?
Claude Code browser paneNo. A clean profile with "none of your saved logins."Claude "won't bypass CAPTCHAs without your input." Clicking can still loop, for the reasons above.No Anthropic doc says it does. One outside blog says it doesn't.
Claude in ChromeYes. Your own Chrome, logins included."It pauses and asks you to handle it manually."No, and it doesn't need to: it looks like you, because it is your Chrome.
ChatGPT cloud browser (successor to ChatGPT agent)No. It runs on OpenAI's servers."Take over browser" hands control to you. Users report the check looping even during a takeover, with no answer from OpenAI.Yes. It signs every request as coming from chatgpt.com. That only helps on sites that choose to let signed agents in.
ChatGPT desktop built-in browser (Atlas closed 9 August 2026)A separate profileOpenAI warns that some sites "require a CAPTCHA."Unknown
Gemini in ChromeYour Chrome, or a remote one"Take over task" / "Give back task"Not documented
Microsoft Copilot Cowork / EdgeYes. Your own Edge profile.Hands you the tab "when a CAPTCHA or human-verification prompt appears."Not documented
Perplexity CometIts own browserNo vendor statement foundA security firm says no. In August 2025 Cloudflare caught Perplexity's crawlers hiding who they were, and removed them from its verified list.
Browserbase (verified tier)No. It runs in the cloud.Only let in where the site owner opts inYes. It was a launch partner for Cloudflare's signed-agent program.

Sources: code.claude.com/docs/en/chrome and /desktop (read 2026-09-25); help.openai.com articles 11845367, 11752874, 20001280, 20001371, 20001277; support.google.com/chrome/answer/16821166; learn.microsoft.com Copilot Cowork local browser (2026-09-23); blog.cloudflare.com/signed-agents (2025-08-28) and Perplexity stealth-crawling post (2025-08-04); community.openai.com thread 1336765 (2025-08-07). OpenAI pages were read from search-engine copies because direct fetches got a 403.

External

Proving who you are doesn't mean you get in

Signed agents

Since 28 August 2025, AI vendors can sign each request so Cloudflare knows exactly whose agent it is. The standard is called Web Bot Auth. It became a formal IETF draft on 1 September 2026, and is still only a draft. Signing tells the site who is visiting. It doesn't get the visitor through.

The 1 July 2026 change

Cloudflare folded signed agents into its "verified bots." Being verified no longer means being allowed by default. Site owners now set Allow or Block for three groups: Search, Agent and Training. "Agent" explicitly includes "Gemini or Claude driving Chrome." Since 15 September 2026, new domains block Agent and Training traffic on pages that carry ads. Reports that older free-plan sites got the same default aren't confirmed.

developers.cloudflare.com web-bot-auth, verified-bots and signed-agents pages (2026-07-01); blog.cloudflare.com/content-independence-day-ai-options (2026-07-01); datatracker.ietf.org draft-ietf-webbotauth-httpsig-protocol (2026-09-01); PYMNTS (2026-09-17). High confidence, except the free-plan claim.

What you can do, best first

  1. Use your real Chrome with Claude in Chrome. Tick the box yourself, then let Claude read the page. This is the route Anthropic documents, and it's the rule we already use for Podbean.
  2. Stay in that one browser once you're through. The pass lasts about 30 minutes by default, and only in the browser that earned it. Switching to the pane starts over.
  3. Keep Cloudflare-checked sites out of the Claude Code pane on Windows. It loops, and sometimes it crashes the app.
  4. Look for another way in: an official feed, a download, or an archived copy. Our internal fallback order is archive sites, then the site's own feed or API, with a real browser last. gameuidatabase.com has none: /api/ returns "not found," and the About page offers only donations and screenshot submissions.
  5. Ask the site owner, for sites that welcome AI. The owner can set the Agent group to Allow, add a skip rule for signed agents, or turn off Bot Fight Mode, which a skip rule can't override. gameuidatabase.com has already said no to AI bots in its robots file.
  6. With cloud agents, use takeover mode: ChatGPT's "Take over browser" or Gemini's "Take over task." Users report it still loops sometimes.

Left out on purpose: stealth plugins, programs that fake a normal browser, and paid services that solve challenges for you. They exist to beat bot detection, and they're out of scope.

Internal

What ForgeFX already knows

WhereWhat it says
Podbean skill, lines 33–36, 20–21 September 2026After repeated automated requests, Podbean showed a Cloudflare check that "loops on forever" in the pane. The rule since then: do that page in real Chrome.
Forge Island devlog, 21 September 2026An agent refused to get around the bot check even with your OK. It used the saved login to list episodes instead, and opened normal Chrome so you could sign in.
Blocked-page recovery skillThe order to try when Cloudflare blocks a page: two web archives, then a reader service, then the site's API, with a real browser last. The reader service's free tier now hits its own Cloudflare check.
LinkedIn and Walmart skillsStop and report at a CAPTCHA. Never try to beat it.
Our own Cloudflare setupForgeFX's Vercel sites are set to "DNS only" in Cloudflare, so Cloudflare's bot checks don't run on our own sites. Nobody has written down our firewall rules yet; it's an open to-do.
Game UI Database skillAnother session created it on 25 September 2026. Right now it's an empty placeholder.

Not searched: Slack and Fireflies. This is a general tooling question, not a client or project one. Only the repo and saved notes were searched.

External

Community reports

SourceDateWhereWhat brokeCause foundFix maintainers back
T3 Code PR 7110 + repro2026-08-15, merged 09-12Electron preview paneError 600010, widget rebuilt every 3.3 sAny rewritten browser name fails, even one that only drops "Electron". Remote-control connection, preload script and graphics card were all ruled out.Keep the app's own browser name
Orca PR 187492026-09-05Electron built-in browser600010, or stuck on "Just a moment"Claimed Chrome without Chrome's matching details. Removing the remote-control connection alone didn't fix it.Honest browser name, and less remote control
claude-code 686742026-06-15, openClaude desktop, WindowsVerification loop on claude.ai itself. Chrome, Edge and Firefox pass on the same connection.None from AnthropicNone
claude-code 920942026-09-04, openClaude desktop and Chrome, MacLoop; Safari passesUnclear. The connection runs through a data center.None
claude-code 80444 (+ 80306, 88335, 90418, 90461, 90732)2026-07-22 to 09-15Browser pane, WindowsWhole app crashes on a Cloudflare-checked pageUsers traced it to a Windows security rule that blocks a graphics file Cloudflare's check loads (81341)Marked fixed 2026-09-15 with no note. One user couldn't reproduce it on version 1.52386.3.
claude-code 169872026-01-09Claude in Chrome, with Chrome started from IntelliJ in debug modeEndless checkUnusual launch settingsStart Chrome normally
puppeteer 110462023-09-27Visible Chrome under Puppeteer control, human clicksFails. The same click without Puppeteer passes.DetectionOnly fixes offered were evasion tools (left out)
playwright 208522023-02-13PlaywrightChallenge blocks testsDetectionTest against a copy of the site without the challenge
chrome-devtools-mcp 5532026-01-08Google's browser-control tool for AIBot blocks—Google decided not to add stealth
OpenAI forum2025-08-07ChatGPT agentLoops, even during takeoverNo staff replyNone
Game Developer2024-09-09gameuidatabase.comOpenAI's crawler hammered the site for about two weeks. The owner called it "essentially a two-week long DDoS attack."—The owner blocked OpenAI's addresses and tightened the robots file

From GitHub and forum searches, 25 September 2026. Cloudflare Community threads block scripted reading, so the two about open DevTools and Electron are left out of this table. Their snippets say having DevTools open can cause error 600010 even after a human passes.

Still unknown

  • Which of Cloudflare's rules on gameuidatabase.com sets off the challenge: a speed limit, a bot score, or a named-bot rule. Only the site owner can see that.
  • Whether the pane's rewritten browser name is what sets off the loop for you. A plain request using that name got through. But the real check runs inside the page, where T3 Code and Orca showed a rewritten name fails.
  • What exactly the pass cookie is tied to: IP address, browser name, or connection details. Cloudflare doesn't publish it.
  • Which signals Cloudflare uses to spot remote control today. Outside researchers disagree, and Cloudflare doesn't say.