All activity
Billy Enrizkyleft a comment
Concentrate or Collapse: When Reinforcement Learning Meets Diffusion Language Models for Web Planning: https://doi.org/10.13140/RG.2.2.11500.94088 Browser-in-the-Loop: Reinforcement Fine-Tuning LLM Agents for Web Form Filling: https://doi.org/10.13140/RG.2.2.24922.71360
OpenBrowser-AIConnect AI agents to browser through raw CDP
Billy Enrizkyleft a comment
Check out our documentation here: https://docs.openbrowser.me
OpenBrowser-AIConnect AI agents to browser through raw CDP
Billy Enrizkyleft a comment
Check out all the 12 trained models here: https://huggingface.co/billyenrizky
OpenBrowser-AIConnect AI agents to browser through raw CDP
Billy Enrizkyleft a comment
Check out our GitHub here: https://github.com/billy-enrizky...
OpenBrowser-AIConnect AI agents to browser through raw CDP
Billy Enrizkyleft a comment
Check out our website at https://openbrowser.me/
OpenBrowser-AIConnect AI agents to browser through raw CDP
OpenBrowser connects AI agents to browser through raw CDP. No abstraction layer. The LLM writes Python in a persistent namespace, batching operations per call. Page state at ~450 characters.
Benchmarked against 3 frameworks on 6 real tasks: 100% accuracy across the board, 2.6x fewer tokens, 59% lower inference costs. Methodology is public and reproducible.
MIT licensed. CLI + MCP server. 15 LLM providers. Two published RL studies training open-source models for browser control.
OpenBrowser-AIConnect AI agents to browser through raw CDP
Billy Enrizkystarted a discussion
Same model, same tasks. 4 browser automation tools used wildly different amounts of tokens. Why?
I watched Claude read the same Wikipedia page 6 times to extract one fact. The answer was right there after the first read. But something about the tool interface kept making it look again. That got me curious. If every browser automation tool can get the right answer, what actually determines how much it costs to get there? So I ran a benchmark. 4 CLI browser automation tools. Same model...
Billy Enrizkyleft a comment
We built OpenBrowser because we wanted to see what happens when an AI agent talks directly to Chrome. Most browser automation goes through an abstraction layer between the LLM and the browser. We took a different path: raw CDP (Chrome DevTools Protocol). The LLM writes Python code that executes in a persistent namespace, batching multiple browser operations into a single tool call. Page state...
OpenBrowser-AIConnect AI agents to browser through raw CDP