Everything you need to know about browser automation
Guides, insights, comparisons, and reviews across Playwright MCP, Browser Use, Chrome DevTools MCP, coding agents, and the browsers they drive.
GuidesCodex Chrome Extension: Setup, Permissions, and Fixes
The official browser-extension path used by Codex, with current setup, supported browsers, permissions, troubleshooting, developer access, and alternatives.
GuidesOpenClaw browser automation: control, relay, and profiles
The official docs now cover more than a browser launch: this guide maps the current setup, profile choice, access boundaries, and the external-tool route for a separate logged-in browser.
GuidesSelenium MCP: Setup and When to Use Playwright MCP Instead
The split that settles this: existing Selenium Grid and test suites justify a Selenium MCP; greenfield agent automation doesn't. Server inventory, full setup, and the migration question answered straight.
GuidesHermes Browser Extension: Connect Agents to Your Browser
Hermes can reach a local browser through several layers. This guide separates the community extension from the Hermes runtime, then compares extension, gateway, CDP, CLI, and ego (lite) by setup, sessions, and tab ownership.
GuidesPlaywright MCP Setup Guide for Claude Code and Cursor
Run Playwright MCP in Claude Code, Cursor, or Codex in five minutes. Compare its snapshots and profile model with Chrome DevTools MCP and a zero-config browser before you choose.
GuidesCursor browser automation: MCP, fixes, and alternatives
Know the built-in Browser's real boundary before debugging around it: per-workspace isolated state, approval-gated tools, and no automatic inheritance of your personal logins. The three routes beyond it, plus fixes for common failures.
GuidesHow to reduce MCP token usage: 6 proven tactics
Most MCP optimization advice targets tool definitions. For browser servers, the real bill is page snapshots. Six tactics, each with before/after numbers and the situations where it applies.
GuidesGoogle Antigravity browser automation: setup and fixes
The architecture explains both the magic and the failures: a Browser Subagent, a deliberately separate Chrome profile, a two-layer URL security model, and Remote Control for reaching sessions from another browser. Configure it right, fix it fast, know its edges.