bb-browser: No Scraping, No API Keys — Your Browser Is the API

Originally published at recca0120.github.io Want Twitter search results? Traditional approaches give you three paths: apply for an API key (rate-limited), write a scraper (get IP-banned), or use Playwright with a headless browser (detected as non-human). bb-browser takes a fourth path: use the Chrome you already have open. You're logged into Twitter, the cookies are right there, and bb-browser runs fetch() inside that tab. From the website's perspective, it's just you browsing. How It Differs from Scrapers and Playwright Let's get the differences clear. bb-browser Playwright / Selenium Scrapers (requests, Scrapy) Browser Your real Chrome Isolated headless browser No browser Login state Already logged in Must re-login or inject cookies Manual cookie handling Anti-bot detection Invisible (it IS the real user) Easily detected Easily blocked Fingerprint Your real fingerprint Headless browser fingerprint No fingerprint The key insight: bb-browser doesn't launch a new browser instance. It co