remote browsers and tab pooling in haylxon

I've been working on haylxon for a while now. It takes screenshots of URLs from the terminal using Chrome's headless mode, talking to Chrome over CDP (Chrome DevTools Protocol). I even gave a talk about it at PTN 11. It was already pretty fast. But I kept noticing things that bugged me about how it worked under the hood. what was bothering me Every time you ran hxn, it would spin up an entirely new Chromium process. Boot it. Wait for it. Connect via CDP. Do the work. Kill it. That browser startup alone eats 300-500ms. If you're screenshotting a handful of URLs, most of your time is just... waiting for Chrome to exist. The other thing, for every single URL, haylxon would open a fresh tab, navigate to the page, take the screenshot, close the tab. Open, close, open, close. Each of those is a CDP round-trip. Felt wasteful. Why not just reuse the tab? And then there was the bigger question I'd been sitting on for a while: why does haylxon need to launch Chrome at all? What if Chrome is…