Menu

1 / 2

🧩 Runtime Snapshots #16 β€” The Three Architectures of Browser Agents

DEV CommunityΒ·AlechkoΒ·7 months ago
#FbG0dgvE
#approach#ai#webdev#mcp#browser
Reading 0:00
15s threshold

Every team building an AI agent for the browser is making one architectural choice β€” whether they realize it or not. They're choosing how the LLM perceives the page. That choice cascades into everything else: cost per action, reliability on real-world apps, what gets banned by anti-bot systems, what kinds of tasks are even feasible.

The choice currently breaks down into three approaches. They're often discussed as if they're competing technologies. They aren't. They operate at different abstraction layers, with different tradeoffs, suitable for different jobs. Mixing them up is the source of a lot of recent disappointment with "browser agents that don't work."

This post lays out the three cleanly: what each one actually sees, where each shines, where each collapses.

Approach 1: Vision-Based Perception

The agent receives a screenshot of the browser viewport. A vision-capable LLM identifies elements visually and responds with coordinates.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.