This week, Browserbase open-sourced Autobrowse — a browser agent that learns a target site through 3–5 iterations, writes the discovered path to a markdown file, and the next agent reads that file before starting. Each iteration costs less. Each iteration finds endpoints the previous one missed. The release has been received as a productivity tool. It is also a structural shift in how the offensive side of bot management works — and most defensive infrastructure has not caught up. This article explains why the implications are larger than the release suggests, and what the receiver side has to do differently from this point forward. What changed Until the past few weeks, the assumption underlying nearly all bot management was that automated traffic was stateless. A scraper started from zero on each session. It would attempt requests, get blocked or rate-limited, and either succeed within the constraints of its programmed logic or fail visibly. That assumption let signature-based detection work.…