· ai-devtools

3 Ways AI Agents Already Operate in Your Browser

Which AI agents can act inside your employees' browsers today?


If an agent started browsing this morning, would you know it wasn't the employee? Most security teams can't answer those questions yet. That's not a failure of effort.

It's a sign of how quickly AI moved from answering questions to taking action. AI agents now operate browsers inside authenticated applications, and they get there in different ways: debugging interfaces, extensions, agentic browsers, and emerging standards like WebMCP. Each changes what an agent can access, how its actions are attributed, and whether existing controls can see them.

One way AI agents operate browsers isn't new at all. CDP was built to help developers inspect, debug, and automate Chromium-based browsers. It provides programmatic access to navigation, page content, network activity, and user interactions. Tools like Playwright and Puppeteer have used it for years.

Earlier coverage

Related coverage

Also worth reading

  1. Angular 20.3.35 and 21.2.26 released, fixing downgraded component template compilation
  2. next.js 16.4.4 released
  3. next.js 16.5.0-canary.35 released with error handling fixes, cache fixes, and docs clarifications
  4. Next.js 16.5.0-canary.33 released, stopping error inspection patching when source maps are disabled
  5. AWS installs an AI accelerator every 14 seconds and eyes $1 trillion annual revenue