the browser layer is why your web agent gets blocked, not the model

Reddit r/AI_Agents Tools

Summary

The article explains that web agents are blocked due to inconsistent browser fingerprinting rather than the model or headless setup, and introduces pydoll, a Python library using Chrome DevTools Protocol for undetected automation.

So most agents that browse the web get blocked the moment they touch a real site, and people blame the model or headless. i been testing what actually flags them and it is the fingerprint not being coherent. a plain headless chrome scored 100 out of 100 on the detection tests, full bot, but the same run with a profile matched to the machine dropped to 15, same as a normal browser. a wrong profile is even worse, a windows profile on my mac scored 57, worse than injecting nothing at all, because one signal disagree with the rest. and none of this touches the network side, your TLS and your IP stay real, so you match the profile to the machine you run on instead of faking everything. i maintain a python lib called pydoll for this, it drives chrome straight over CDP with no webdriver, async, so an agent can run many tabs and intercept requests without the usual automation tells. the fingerprint injection is the part that keeps a browsing agent from getting blocked
Original Article

Similar Articles

Known By Their Actions: Fingerprinting LLM Browser Agents via UI Traces

Hugging Face Daily Papers

This paper demonstrates that websites can identify which large language model powers a browsing agent by analyzing its behavioral patterns and timing data, achieving up to 96% F1 score across 14 frontier LLMs. It formalizes this attack surface and shows that random timing delays are insufficient to prevent identification.

BrowserAct

Product Hunt

BrowserAct is a web browser automation tool designed for AI agents, enabling automated web interactions.

AI agent security is a small prayer the model says no. How are you routing models?

Reddit r/AI_Agents

The author conducted an experiment on Gmail with AI agents connected via OAuth, sending obfuscated prompt injection emails. Frontier models sometimes caught the attacks, while cheap models silently executed them, revealing that agent security largely depends on model cost and token budget rather than architectural safeguards.