vibium

vibium clicker, too. https://github.com/VibiumDev/vibium/blob/main/CONTRIBUTING.m... "browser automation for ai agents" is a popular idea these days.

I commented your project in this thread lol, but since my account has low score the comment is probably hidden to most folks, so thanks for sharing about Vibium here. I'm following your progress since I asked a similar "Ask HN" a couple of weeks ago, it's been interesting checking your (and Claude's) work/commits on https://github.com/VibiumDev/vibium/commits/main/

https://github.com/VibiumDev/vibium/commits/main/ This is a new browser-testing library by the creator of selenium, apparently all code commits are co-authored by claude, I'm following this repo to see how far this strategy will go

I may not be understanding the the context of #3 (Javascript console, page contents showing traceback?), but I'd be looking at MCP servers for Playwright or https://github.com/VibiumDev/vibium or that browser automation MCP that I think Google announced a month or so for Chrome and the name of which escapes me.

For right now, the MCP server doesn’t expose quite enough to navigate on its own. I’ve added a browser_evaluate tool in my fork—though I haven’t committed or pushed a PR yet. With that, the agent can call JavaScript to get the accessibility tree and then use that to navigate via browser_find. This and much more will be coming soon. See the V2 roadmap for more insight: https://github.com/VibiumDev/vibium/blob/main/V2-ROADMAP.md

- No LLM Getting Started with Vibium (beginner-friendly): https://github.com/VibiumDev/vibium/blob/main/docs/tutorials... - MCP option (where tokens will eventually get burned) Getting Started with Vibium MCP: https://github.com/VibiumDev/vibium/blob/main/docs/tutorials...

it will be more obvious in v2. v1 is about getting to a base-line of functionality. things get interesting in v2: https://github.com/VibiumDev/vibium/blob/main/V2-ROADMAP.md

> why the MCP server doesn't expose a JavaScript/eval tool? no reason other than my number #1 goal was "ship something". i only started the actual coding on dec 11. it's been a bit of a sprint the last two weeks! though "image-based" vs "dom-based" testing approaches is a very big topic! (look forward to researching that more in the future.) v1 announcement: https://github.com/VibiumDev/vibium/blob/main/docs/updates/2...

Aside from the project itself, I am learning a lot just from reading the commits. Mostly about the process when one knows how they'd do it. https://github.com/VibiumDev/vibium/commits/main/?after=ffc3...

i partially addressed this in the "why vibium" section of the v1 announcement: https://github.com/VibiumDev/vibium/blob/main/docs/updates/2... but why a new thing vs extending selenium? it's a little complicated, but neither selenium nor playwright were designed with ai in mind from day 1. with vibium, i'm optimizing for "vibe coding" and ai-driven workflows first.

I wasn’t able to gather the future state plans beyond what’s noted in the V2 plans: https://github.com/VibiumDev/vibium/blob/main/V2-ROADMAP.md What’s next 5 years look like given that you are very good at building long-term projects that last and evolve through time? And for a very specific example, what’s the plan for incorporating new standards like Agent Skills as they quickly evolve and launch?

it's a good questionn! i partially addressed this in the "why vibium" section of the v1 announcement: https://github.com/VibiumDev/vibium/blob/main/docs/updates/2... to save a click, i'll post it here, too: ----------- why vibium? there are dozens of "ai-powered browser" tools now. so why this one? the selenium ecosystem is massive: millions of tests, thousands of companies, decades of investment. but there's no obvious bridge to the ai future. many have moved to playwright — and for good reason: it's fast, easy to use, has popular features like auto-waiting, integrated video recording, and a ton of other batteries included. vibium takes the same approach. batteries included. great dx. but built for where the industry is going: ai agents that need to drive browsers. when i did those interviews in september, the response wasn't just "cool

i started the selenium project 21 years ago. vibium is what i'd build if i started over today with ai agents in mind. go binary under the hood (handles browser, bidi, mcp) but devs never see it. just npm install vibium. python/java coming. for claude code: claude mcp add vibium -- npx -y vibium v1 ships today. ama.