logoalt Hacker News

Show HN: Agweb – a browser for agents that stays out of your way

62 points • by paul_nameless • today at 2:08 PM • 19 comments • view on HN

Comments

CharlesW • today at 3:43 PM

Out of curiosity, what prompted you to make this when agent-browser.dev and lots of other alternatives already exist? "Because it's fun" is absolutely a legitimate answer, but I couldn't tell from the README what I might be missing.

➕ show 1 reply
bensyverson • today at 4:29 PM

I love it! I’m going to give this a try for sessions that need to do a lot of browsing. If anyone is looking for a headless WebKit browser/viewer for agents (more focused on development), check out https://github.com/bensyverson/sleepyhollow

farhankhan3 • today at 5:41 PM

I built something similar (albeit didn't put too much effort in), so will be moving to this! Great work.

➕ show 1 reply
bookernath • today at 3:15 PM

Great work, I'll try it out as a replacement for chrome for my verification flows today. It's great to have ad blocker but it's curious to me to enable it by default, is this something you use more for scraping than application testing for example?

Onavo • today at 6:54 PM

Are the UBlock Origin lists configurable and is the browser stealthy enough to been indistinguishable from normal chrome when used from a residential IP?

7777777phil • today at 3:48 PM

> agweb has no automatic cookie-banner remover. Its ad blocker uses uBlock Origin’s lists, which block ads and trackers but leave consent dialogs alone

this is awesome

➕ show 1 reply
paul_nameless • today at 2:11 PM

I run several agents at once. Playwright's Chrome windows kept popping up and grabbing my keyboard, and headless got blocked by some sites and you can't see easily what's happneing.

agweb keeps what's good about headless and still lets you watch. It never pops up or takes focus, and idle tabs get suspended: five idle pages sit at 0% CPU and 590 MB, vs 1.6 GB for Playwright's Chrome. ⌘D shows every agent's tabs live.

For agents, the commands mirror playwright-cli, which they already know. Each reply also says what the action changed (fetches, elements added or removed), so they need fewer snapshots, fewer tool calls and fewer tokens.

Also: one login shared by all agents through a named profile, fill --secret-cmd 'pass show site' keeps passwords out of the transcript, and ask hands the tab to you for MFA or a CAPTCHA.

macOS 26+, WebKit only, no CDP.

➕ show 1 reply
agline_in • today at 2:48 PM

The shared named profile is handy, but how do you deal with one agent's actions spilling over to the others? For example, one agent logs out, switches accounts, or trips a site's rate limit, and every other agent on that profile inherits it. Is there a way to give an agent a forked or read-only copy of the profile's cookies?

➕ show 2 replies
musclehed03 • today at 5:34 PM

[flagged]