Rendered at 19:43:47 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
edmundsauto 2 days 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.
murrrrrph 1 days ago [-]
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.
icyfox 1 days ago [-]
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):
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.
esteka 1 days ago [-]
"because it's fun" is a highly underutilized reason
kevsamuel 2 days ago [-]
What alternative show you a visual preview like this?
CharlesW 2 days ago [-]
I assume all can do this for human-in-the-loop scenarios. I've personally settled on agent-browser.dev for now.
fastball 2 days ago [-]
agent-browser uses chrome test mode or whatever it is called, which means a bunch of stuff gets broken by bot detection.
CharlesW 2 days 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.
nitin0gai 15 hours ago [-]
[dead]
pklym 1 days ago [-]
[flagged]
vishwakulkarni 1 days ago [-]
How are you planning to handle multiple agent sessions running concurrently? Agents can jump into other session! possibilities are high
bensyverson 2 days 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
dfish 2 days 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.
anigbrowl 2 days 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.
bookernath 2 days 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?
pklym 1 days ago [-]
With ad blocker it is less context for ai, faster and less ram usage (rules size is less than some ad blockes). I use it to automate things in work and personal life, debugging, testing frontend, running auto tests.
Axsuul 1 days ago [-]
I’m looking for something similar to this but can be self hosted in the cloud. Any suggestions?
icyfox 1 days ago [-]
What's your specific usecase? Just general browser as a service?
There are a ton: kernel, browserbase, browser-use.
Any more requirements other than cloud hosted?
Axsuul 20 hours ago [-]
Thanks for chiming in! It needs to be self-hosted/open source, and a platform that can be used by any agent (via OpenCode) as well as through Hermes Bot Screen. I need to also be able to take over the browser/screen to login, fill out captchas, etc (just like Grok Bot). Does that help?
Onavo 2 days 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?
pklym 22 hours ago [-]
Lists only via env for now, AGWEB_ADBLOCK_LISTS. It's real WebKit and says Safari, not Chrome. Clicks and typing are native events at human pace, no fingerprint spoofing though.
7777777phil 2 days 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 2 days ago [-]
What's good about cookie consent dialogs?
theK 2 days ago [-]
A lot of pages don't work when an adblocker removes the Dialog.
derefr 2 days 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.)
farhankhan3 2 days ago [-]
I built something similar (albeit didn't put too much effort in), so will be moving to this! Great work.
pklym 2 days ago [-]
Thanks!
mentalgear 2 days ago [-]
is there a cli version / headless or build on such.
_blk 2 days ago [-]
Looks interesting! But..
> Needs macOS 26 or later.
Too bad. I'll check back when someone submits a PR for Linux.
pklym 1 days ago [-]
PR is welcome, happy to support it!
paul_nameless 2 days 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 2 days 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 2 days ago [-]
Probably because it’s not chromium
pklym 2 days 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.
Innoraai 7 hours ago [-]
[dead]
RowanHuang 7 hours ago [-]
[flagged]
agline_in 2 days 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 2 days 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 2 days 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.
It's one browser, so the agent and I share it, so it doesn't pass your fourth point.
https://github.com/MonkeySee-AI/rotunda
Linking if helpful.
> 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.
this is awesome
> Needs macOS 26 or later.
Too bad. I'll check back when someone submits a PR for Linux.
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.