Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The big features I need in an agentic browser.

1. Not detectable and so not blocked 2. Uses my IP (I have separate hardware available) 3. Uses cookies from my main browsing sessions 4. Run in parallel-shadow so it doesn’t block me, I don’t break it.

We are in the cat and mouse world of scraping, but with end users now. Companies that enable agents will thrive and those that don’t, won’t.

I also wonder how much of a SMB profit margin comes from upsells and dark patterns. Agents help me a lot with avoiding those, also reducing my cognitive complexity. I’m at the point where I don’t order things if I can’t delegate my agent, I don’t want to see all their bullshit that they’ve structured to extract more money from me. My agents save me from those costs.

 help



My setup covers your first three, though not with a dedicated agent browser. The agent (Claude Code) drives an ordinary Chrome that I use myself, through the Chrome DevTools Protocol (CDP). That Chrome is started with its own profile and Chrome's remote-debugging switch, and I'm thus automatically logged into Gmail, Slack, shops etc. So it's my IP, my cookies, and the browser that shops don't block. The agent opens a temporary tab, reads what it needs, and closes it - unless it needs to leave it open for me to actually make the purchase.

It's one browser, so the agent and I share it, so it doesn't pass your fourth point.


Seems like we share the same frustrations with most dedicated agentic browsers. I maintain an firefox fork that does all of this (cookie syncing you can perform manually via the API when you'd like):

https://github.com/MonkeySee-AI/rotunda

Linking if helpful.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: