the fork report: SELENIUM by seleniumhq
the blueprint for automation
the signal
while the world is currently obsessed with “ai agents,” builders are still quietly forking the tool that started it all: selenium. it has over 8k+ forks.
this repo is the foundation. long before we had autonomous ai driving our browsers, we had selenium. builders fork this today because it is the most robust way to interact with a browser at a low level. whether you are building a complex web scraper or a custom testing suite, selenium is the engine under the hood that makes it possible to scale.
what it is
selenium is an open-source umbrella project for a range of tools and libraries used for browser automation.
it works via a webdriver. think of this as a remote control for your browser. it provides a common interface for your code to “talk” to chrome, firefox, or safari. instead of an ai “guessing” where to click based on pixels, selenium uses the dom (document object model). that is the internal skeleton of a webpage. it lets you target a specific button or text field with surgical precision.
why it matters
this project is personal for me. it is actually the one that got me started in coding back in 2018. back then, stack overflow was the only place to find answers, and you could spend six hours in a dark room trying to debug a script just to realize you were missing a close bracket.
the reason forking selenium is still a power move is control. modern tools like playwright or puppeteer are great, but selenium’s grid system allows you to run tests across different machines and operating systems at the same time. it is the industry standard for a reason. if you want to understand how the web actually works, and how to break it, you start here.
what you can do with it today
go back to the basics to understand the future.
the 5 minute win: install the selenium library for python or javascript. write a ten-line script to open your favorite news site, search for a keyword, and save the headlines to a text file. it is a reminder of how satisfying it feels to watch a browser move on its own.
the build: if you are currently building an ai agent, use selenium as the fallback layer. when the ai gets confused by a complex layout, give it a selenium script to handle the “dirty work” of navigating through legacy login screens or multi-step forms
keep on forkin!
building with grace is a daily ish newsletter about ai, building, and the chaos in between.