BrowserOS vs Yad

BrowserOS is an open-source Chromium-based browser with AI agents for carrying out web tasks from natural-language directions. The agents can navigate, click, type, fill forms, extract data, and run workflows across multiple steps. Chat Mode answers questions about the page in view; visual Graph Mode for repeatable workflows is marked as coming soon. BrowserOS supports Gemini, Claude, OpenAI, and local models through Ollama or LM Studio. Its maker lists more than 40 MCP app integrations, including Gmail, Slack, Notion, and Calendar, as well as 53 built-in browser tools. An included MCP server connects with Claude Code, Gemini CLI, or Codex. As a Chromium fork, it supports Chrome extensions and import of Chrome bookmarks, passwords, and settings. Browsing data stays on-device unless cloud syncing is enabled; syncing is off by default, and synced activity is encrypted on BrowserOS servers. BrowserOS says it does not store or log AI prompts or responses, though providers may handle submitted data under their own policies. It is free and licensed under AGPL-3.0.

Yad turns plain-language instructions into actions in your own logged-in browser. It can click, type, navigate websites, fill forms, and handle research tasks, with human approval steps and scheduled tasks. The extension works in Chrome and Brave alongside a free companion app that currently runs only on Windows. You can bring an AI provider key or use a local model; listed options include Groq, Google Gemini, OpenRouter, and custom endpoints. Yad stores selectors, past runs, and learned fixes on your device for reuse, and the companion exposes a local API accepting goals at POST localhost:3747/goal. The maker says passwords, card numbers, and sensitive page fields are masked before content reaches an AI; local-model use keeps page content on the computer. The companion encrypts the AI key with Windows DPAPI, while the extension stores only the encrypted blob. Spending caps and one-click stopping are available, and payment or checkout pages are blocked from autonomous action. Hosted team setups require contacting Yad and cannot use personal logged-in sessions.