Hey Product Hunt! 👋 I’m Vaibhav, Founder at Kubar Labs. I recently asked X for a recommendation: I needed a CLI-based headless browser designed specifically to work with AI agents. I was tired of existing solutions treating agent integration as an afterthought. The market had no good answer. Every solution was either a heavy testing framework repurposed poorly (like Playwright), or a raw protocol wrapper that broke at the slightest breeze. When we tried to automate workflows in the background, our agents either lost access to their cookies, hallucinated CSS selectors on React sites, got blocked by Cloudflare, or left zombie Chromium processes hoarding our RAM. So, we built it ourselves using bare-metal Linux primitives. Introducing the Agent Bulletproof Browser Automation Kit. It is an enterprise-grade bash wrapper and AI Skill that completely insulates your agents from browser automation hell. ✨ What makes it bulletproof? 1. The "Chain of Death" (prctl): Biologically tethers the Chromium process to the agent's execution script. If the agent gets OOM-killed or hard aborted, the OS instantly vaporizes the browser. Zero orphaned memory leaks. 2. Safe Concurrency (flock): Queues multiple subagents so they don't crash the profile database or steal tab focus from each other. Bot Cloaking: Native --headless=new and User-Agent spoofing completely bypasses WAFs and navigator.webdriver footprinting. 3. Vision-First Policy: The included SKILL.md teaches your agent (Hermes, OpenClaw, Claude) to stop hallucinating DOM selectors and use coordinate-based clicking via screenshots instead. It’s completely open-source. If you use Hermes or OpenClaw, you don't even need to use the terminal, just paste the prompt from our README and the agent will install it autonomously. I’d love to hear your thoughts. What’s the most frustrating part of browser automation for your agents today? Drop your questions below, I’ll be hanging out here all day answering them! 👇

Forum Threads

p/agent-bulletproof-browser

•

16h ago

What’s the worst browser automation fail your AI agent has caused?

We built the Agent Bulletproof Browser because our AI agents kept leaving "zombie" Chromium processes running in the background, completely hoarding our RAM and locking up our ports. We were using heavy testing frameworks (like Playwright) that just weren't meant for asynchronous agentic workflows.

Before we went down to the bare-metal Linux level to fix it, we had agents hallucinating CSS selectors and getting shadow-banned by Cloudflare.

What s your worst horror story with agents trying to browse the web? Curious to hear what workarounds you're currently using!

View all

Agent Bulletproof Browser

The 100% stable, headless browser kit for AI agents

The 100% stable, headless browser kit for AI agents

Forum Threads

What’s the worst browser automation fail your AI agent has caused?

Forum Threads

What’s the worst browser automation fail your AI agent has caused?