Introducing the new dev-browser cli.
The fastest way for an agent to use a browser is to let it write code.
Just `npm i -g dev-browser` and tell your agent to "use dev-browser"
VIDEO
there are like 100s browser agent clis (even Garry Tan has one) why use this one?
dev-browser is incredibly bitter-lesson pilled. Rather than inventing a new syntax for browser automation, just use the one they already know: Playwright.
dev-browser is incredibly bitter-lesson pilled. Rather than inventing a new syntax for browser automation, just use the one they already know: Playwright.
the original dev-browser was just a markdown file and a few scripts that called playwright directly. simple, but slow startup and you had to let your agent run arbitrary node scripts. since its release there has been a lot of innovation in the browser skill space (from things like agent-browser)
the new cli addresses the two biggest points of feedback from the original: a proper daemon for fast startup and all playwright scripts run inside a sandboxed quickjs vm. your agent writes real playwright code but can't `fs.rm()` because it had a bad day.
the new cli addresses the two biggest points of feedback from the original: a proper daemon for fast startup and all playwright scripts run inside a sandboxed quickjs vm. your agent writes real playwright code but can't `fs.rm()` because it had a bad day.
Generated by Thread Navigator
Press ⌘ + S to quick-export