AI Blog

Tagged: browser-agents

← Back to AI Blog

9 min read

United Banned the Supervised Agent Too, and That Is the Whole Lesson

United's revised Contract of Carriage, dated 11 November 2026, bans AI agents from buying, changing or servicing a ticket even where the passenger oversees and approves the action — and no outlet covering it could say how the airline intends to detect an agent at all. That combination is the design statement: when the predicate is unobservable, the only control left is a remedy, so enforcement moved to a right to cancel the booking without notice. Fare search stays open because a read has nothing to reverse. Put your prohibition one layer upstream of the first irreversible step, or you have a preference rather than a policy.

10 min read

OSWorld vs WindowsAgentArena vs AndroidWorld vs BrowserGym: the verifier is the benchmark

These four get quoted as four measurements of the same ability, and they are four different objects. Two of them do not own a verifier at all: WindowsAgentArena vendors OSWorld's metric library wholesale, and BrowserGym is a harness that imports whatever the wrapped benchmark wrote. The axis that decides whether a score transfers is not the operating system or the task count — it is what the check reads. OSWorld compares a saved file against a gold copy after pressing Ctrl+S itself; AndroidWorld reads device state on a randomised instance no other run shares; BrowserGym's reward float carries a binary page check in one row and a token-bag F1 in the next.

10 min read

The front door closed; the MCP server did not

Amazon, Yelp, Delta, JPMorgan and Schwab all shut third-party AI agents out within four weeks, and every one of them left a different door open. Schwab published both halves of the rule on its 14 October earnings call: agents arriving with a client's password are blocked, while outside models may read balances and research through Schwab's own MCP servers and may not move money. What is being refused is not automation and not AI — it is credential delegation, which no bot-identity standard can fix, because an agent holding the user's password is indistinguishable from the user by design.

10 min read

Safari MCP vs Chrome DevTools MCP vs Playwright MCP vs extension agents

Tool counts decide nothing here. The axis that determines both whether a browser agent can do the job and how bad a hostile page gets is which session it holds — an isolated automation context, a dedicated profile quietly accumulating logins, or your own signed-in browser. Both browser vendors that shipped an MCP server this year deliberately kept your own session out of it, which is why neither does the agentic-shopping demo everyone expected.

9 min read

WebMCP makes your page an API, and the session is the only auth it has

WebMCP lets a page hand an AI agent a list of callable tools, and Chrome is shipping it behind a flag while the W3C community group draft is still moving. The part worth arguing about is not discovery but authority: a registered tool executes as your page's own JavaScript, inside the session the logged-in user already established, so your server sees a request it cannot distinguish from a click. You are publishing an API whose only credential belongs to someone who is not the caller.

9 min read

Gemini Spark moved into your Chrome profile, and the handback is on the wrong line

Google’s agent now drives the Chrome you are logged into, with your saved passwords, and hands control back for payments. Payment is the one action with a chargeback window; the mailbox read, the data copied out and the recovery address changed are all on the unattended side of that line.

8 min read

Cloudflare’s Kitesurf makes a browser cheap enough to throw away

The quoted number is 3–7× less CPU and memory than Chromium. The consequence worth planning around is that a fresh browser per task stops being a cost you amortise by reusing sessions — and session reuse is where browser-agent state leaks live. What you trade for it is a compatibility tail that fails silently.

9 min read

Browserbase vs Steel vs Hyperbrowser vs Anchor Browser: You Are Choosing Who Holds the Session

All four speak CDP, so the automation code ports in a day and the SDK comparison decides nothing. The real choice is who holds the logged-in profile, the credentials that recreate it and the exit IP whose reputation you inherit — plus the fact that the latency spread between them is entirely control plane.

9 min read

Atlas Shuts Down on 9 August. Agentic Browsing Just Split Into Three.

OpenAI is retiring the ChatGPT Atlas browser nine months after launch and moving its capabilities into a Chrome extension, an in-app browser and a server-side cloud browser. That is not a retreat from agentic browsing — it is the admission that a browser agent never needed a browser. What it needed was proximity to an authenticated session, and the three replacement surfaces are three different answers to whose session it borrows.

20 min read

Browser-Use vs Stagehand vs Skyvern vs Playwright MCP: Four Answers to How an LLM Should Drive a Web Page

When there is no API, an agent has to drive the browser itself — and four open-source projects disagree on how it should see the page. browser-use reads the DOM, Skyvern looks at pixels, Stagehand lets you dial between code and AI, and Playwright MCP is not an agent at all but the standard browser-tool layer any model can call. Picking one is really two decisions: Python or TypeScript, and a framework or an MCP server.

14 min read

Claude Computer Use (post-Vercept) vs Codex Background CU vs Operator vs Gemini: Four Bets on Letting AI Drive the Mouse

72.5% on OSWorld is the new floor, not a milestone — and three labs have made architecturally opposite bets on where the mouse should live. Pick the wrong one and you fight your sandbox forever; pick the right one and the model does in two minutes what your RPA stack does in two weeks.