Rendered at 05:04:53 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
edmundsauto 3 hours ago [-]
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.
dfish 48 minutes ago [-]
[flagged]
dfish 50 minutes ago [-]
We use agweb daily and love it. It is a good alternative to Atlas that gives you a full desktop (most of our use cases are web, of course), and it doesn't require a new user.
CharlesW 13 hours ago [-]
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.
kevsamuel 12 hours ago [-]
What alternative show you a visual preview like this?
CharlesW 11 hours ago [-]
I assume all can do this for human-in-the-loop scenarios. I've personally settled on agent-browser.dev for now.
fastball 4 hours ago [-]
agent-browser uses chrome test mode or whatever it is called, which means a bunch of stuff gets broken by bot detection.
CharlesW 3 hours ago [-]
It can, but it can also use your personal browser (Chrome and Safari, haven’t tried Firefox).
> Chrome for Testing is the default browser. You can also attach to a running Chrome with --cdp or --auto-connect (CDP mode), select the Lightpanda or Obscura engine with --engine, drive Mobile Safari in the iOS Simulator, or use a cloud browser provider such as Browserbase, Browserless, Browser Use, Kernel, or AgentCore.
The features I look for a persistent sessions, so I can login, visual feedback tools, and low resource usage.
anigbrowl 6 hours ago [-]
Nice! Most of the time I'm doing tests on my own web applications rather than on the open web and focus hijacking during test cycles was becoming a real pain. Plus I resent Chrom*'s outsize footprint.
bensyverson 13 hours ago [-]
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
bookernath 14 hours ago [-]
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?
farhankhan3 11 hours ago [-]
I built something similar (albeit didn't put too much effort in), so will be moving to this! Great work.
pklym 11 hours ago [-]
Thanks!
_blk 4 hours ago [-]
Looks interesting! But..
> Needs macOS 26 or later.
Too bad. I'll check back when someone submits a PR for Linux.
mentalgear 9 hours ago [-]
is there a cli version / headless or build on such.
Onavo 10 hours ago [-]
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 13 hours ago [-]
> 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
jstanley 13 hours ago [-]
What's good about cookie consent dialogs?
theK 13 hours ago [-]
A lot of pages don't work when an adblocker removes the Dialog.
derefr 12 hours ago [-]
I mean, rather than just out-and-out removing them, I would think that the proper thing to do to get those dialogs out of the way would be to have a separate extension that detects them and automatically interacts with them to dismiss them (in whatever way you'd prefer.)
paul_nameless 15 hours ago [-]
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.
jazzypants 13 hours ago [-]
Why would you mirror the playwright CLI but not CDP? This looks pretty cool, but it's completely useless to me without CDP.
alexgoodhart 11 hours ago [-]
Probably because it’s not chromium
pklym 11 hours ago [-]
agweb is the system WebKit, so no CDP. Commands copy playwright-cli bc agents already know them. If you need CDP, Playwright fits better.
agline_in 14 hours ago [-]
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?
tomaskafka 12 hours ago [-]
This - for some scenarios I want the cookies shared (multiple agents watching eg fb marketplace), for others I want to have their own sandbox. And the GUI could indicate this eg. by putting tabs that share profile into blocks.
pklym 11 hours ago [-]
Not yet. For now, state-save in one workspace and state-load in a fresh one gives an in-memory copy, so a logout stays there. Fork flag can be done.
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.
> Chrome for Testing is the default browser. You can also attach to a running Chrome with --cdp or --auto-connect (CDP mode), select the Lightpanda or Obscura engine with --engine, drive Mobile Safari in the iOS Simulator, or use a cloud browser provider such as Browserbase, Browserless, Browser Use, Kernel, or AgentCore.
The features I look for a persistent sessions, so I can login, visual feedback tools, and low resource usage.
> Needs macOS 26 or later.
Too bad. I'll check back when someone submits a PR for Linux.
this is awesome
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.