bookmarks
13 bookmarks

Introducing WebMCP + agent-browser The web is becoming agent-native 𝚊𝚐𝚎𝚗𝚝-𝚋𝚛𝚘𝚠𝚜𝚎𝚛 𝚠𝚎𝚋𝚖𝚌𝚙 <𝚕𝚒𝚜𝚝|𝚒𝚗𝚟𝚘𝚔𝚎> → Discover & call tools → For missing tools, falls back to browser automation↗

ChatGPT Work can now use its computer and browser to sign in to websites on web and mobile, without ChatGPT ever seeing your username or password. That means you can ask it to: • Set up utilities for a new apartment • Book a DMV or passport appointment • Check reimbursement cost…↗

Feel like you could build a new version of Zapier off of MCP/CLI/OpenAPI/fallback to browser use. Charge per run, no subscription, make it fractions of a penny. Interface is a single input, results are the automation with event history on the left and chat on the right. Integr…↗

·@frantzfries·Aug 9, 2026·essay·browser-automation·cli·mcp·openapi

Claude Code on desktop now has an in-app browser. Claude can pull up docs, designs, or any other site. It can read, click through, and interact the same way it does with your local dev servers. It's sandboxed and configurable: you choose whether sessions persist.↗

Now available: agent-browser MCP Same browser automation. New way to plug it into your agent loop. Why you might choose MCP: → You like MCP → You work from UIs like Cursor → You're more hands-on with your agent → Your agent has a browser, but not enough tools↗

Introducing the new dev-browser cli. The fastest way for an agent to use a browser is to let it write code. Just `npm i -g dev-browser` and tell your agent to "use dev-browser"↗