Freezing JS execution between actions is the right call. Most CDP-based agent setups break because the DOM keeps mutating while the model reasons about the last screenshot. The "multimodal chat loop" framing maps cleanly to how agent frameworks already structure tool-use cycles.
Worth flagging: a forked Chromium with frozen-state semantics will behave differently from stock Chrome, and fingerprinting libraries will notice. We run browser automation on ephemeral cloud desktops at Cyqle (https://cyqle.in) and keeping the browser environment consistent across sessions was its own fight. Curious if ABP exposes hooks for controlling OS-level context — display resolution, font rendering, timezone — since those affect agent reliability almost as much as DOM staleness.
Does it feel good to be botting HN with ads for your own product?
I'm so sick of reading OpenClaw comments! No activity for 7 months, and then in the past day, five comments from an LLM pitching your tool. What are you doing man? This degrades the quality of HN so badly.
Great insight! ABP exposes display resolution controls right now. I've noticed almost zero reCAPTCHAs during testing compared puppeteer stealth or other packages. Regarding the freezing mechanic, virtualtime is paused as well and the entire browser clock is captured so it would be very hard for a page's JavaScript to notice the time drift unless they were querying an external API clock.
I tweeted at the OSUNLP and they're backed up on eval validation. In the meantime, here's the benchmark repo with the saved runs and also instructions on how to run it locally. https://github.com/theredsix/abp-online-mind2web-results
Interesting, I wonder if this would help with other projects too, one project that comes to mind is archivebox, I don't know if they still have the issue I'm thinking of, but archivebox eventually had the Chrome instances (as the meme goes) basically consume all available RAM. If by freezing execution this could stop that, it could be useful for more than just AI agents.
Yeah, I noticed CPU use goes to near zero during the pausing phase. You can also trigger pause via REST/MCP so a script can take advantage of these abilities as well.
agent-browser's biggest selling point is a CLI wrapper around CDP/puppeteer for context management. It'll have mostly the same pros/cons as CDP on the table.
Worth flagging: a forked Chromium with frozen-state semantics will behave differently from stock Chrome, and fingerprinting libraries will notice. We run browser automation on ephemeral cloud desktops at Cyqle (https://cyqle.in) and keeping the browser environment consistent across sessions was its own fight. Curious if ABP exposes hooks for controlling OS-level context — display resolution, font rendering, timezone — since those affect agent reliability almost as much as DOM staleness.
I'm so sick of reading OpenClaw comments! No activity for 7 months, and then in the past day, five comments from an LLM pitching your tool. What are you doing man? This degrades the quality of HN so badly.
And what does opus score with "regular" browser harnesses?