Writing log70 posts277 tagslatest Sep 5, 2026
Browser-automation.
Latest posts
WebMCP Explained: What Changes in Browser Automation When a Web Page Hands Tools Directly to an AI Agent?
WebMCP is a W3C Community Group proposal in which a web page registers JavaScript functions and HTML forms as "tools" on document.modelContext, and the browser mediates those tools to the user's agent. This article lays out the imperative and declarative APIs and the boundaries the browser guarantees, straight from the spec, then calls real tools with Chrome 152 and agent-browser 0.36 to see how it differs from accessibility-tree automation.
Analyzing Browser Use: How Do You Show a Web Page to an LLM So It Can Drive a Browser?
Browser Use is a Python agent in which an LLM drives a real browser. It pre-chews the page into an indexed list of interactive elements for the LLM, drives the browser via CDP instead of Playwright, and runs the session with an event bus and watchdogs. We look at why this fits LLMs better, picking up from the earlier Playwright analysis.
Playwright Architecture Explained — Why It Became the E2E Testing Standard
A deep dive into the Playwright repository — covering the core engine, client/server protocol, fixture-based test runner, why it has become so popular, why it feels slow when paired with an LLM, and what the alternatives look like.
Playwright vs agent-browser vs Lightpanda — Which Browser Automation Tool Should You Use?
Playwright, agent-browser, Lightpanda — a comparison of the positioning and key differences among three browser automation tools, with the same task implemented in each, to provide practical guidance for choosing the right one.
agent-browser Architecture Analysis / A Browser Automation CLI for AI Agents
A deep-dive into the architecture of agent-browser, Vercel Labs' Rust-based browser automation CLI for AI agents — covering CDP-based control, the accessibility-tree Ref system, Provider abstraction, and the security model.