Customers

How Composio's Browser Tool Uses Browser Use to Automate Websites Without APIs

Composio Browser Tool runs every task on a Browser Use agent in a managed cloud browser, so agents connected through Composio can log in, fill forms and download files on websites with no API.

Browser Use x Composio

"Browser tasks on Composio grew 125x this year because Browser Use gets past bot detection and CAPTCHAs on its own, so our customers' agents finish the job end to end."

— Sushant Hiray, Head of Solutions, Composio

Composio Browser Tool is the toolkit that lets any agent connected through Composio work on a website the way a person would: log in, navigate, fill forms, extract data and download files. Every Browser Tool task runs on a Browser Use agent in a managed cloud browser. Composio's agents reach more than 1,500 apps through their APIs; Browser Tool covers the part of the web that has no API.

What is Composio Browser Tool?

Composio gives AI agents tools and authentication for more than 1,500 apps. Claude, Codex, Cursor, OpenClaw, Hermes and the other agents people run today connect to Gmail, Slack, Salesforce, Notion and the rest through one platform, with the OAuth flows and key management handled for them.

That covers every app with an API. It does not cover the rest of the web. A supplier portal with a login and a download button, a booking page, a government form, a checkout, a PDF that only exists behind an account: there is no endpoint to call and no webhook to subscribe to. An agent that can only reach APIs stops at the edge of that world and asks the user to finish by hand.

Browser Tool is the toolkit Composio built so the agent does not have to stop. In the Composio catalog it looks like any other toolkit, with five tools: run a browser task, watch it, get a live view of the session, stop it, and download the files it produced.

How Composio Browser Tool works with Browser Use

Behind each Browser Tool task is a Browser Use agent running in a managed cloud browser. The Composio agent describes the job in plain language ("log in to the vendor portal, open this month's invoice and download the PDF"), Composio calls the Browser Use task API, Browser Use runs the browser, and the result and files come back to the agent, which keeps its context and carries on with the next step.

Browser Use takes on the parts that make websites hard to automate:

  • Bot detection and CAPTCHAs are handled inside the session (stealth, CAPTCHA handling).
  • Logins and authenticated pages work, and stay logged in between tasks on a per-customer browser profile.
  • Multi-step flows such as forms, reservations and checkout run to the end.
  • A live view of the session lets a person watch the browser or take over mid-task (live preview).
  • Files produced in the browser are returned to the agent.

Because the two sides meet at the task level, the same Browser Tool works for every agent Composio supports. Composio's own setup guides cover Claude Code, Codex, Hermes and the other agent frameworks it integrates, with no browser-specific setup.

Apps and websites in one agent session

The point is not a browser on its own. It is that the browser sits next to everything else. A Composio agent can enrich a lead from Salesforce over the API, check the company's registration on a state portal in the browser, and draft the follow-up in Gmail over the API, in one session, under one identity, with one place where auth and permissions are managed.

Composio handles apps with APIs and MCPs. Browser Use handles websites without them. Together, one agent can do both.

Why Composio chose Browser Use for browser automation

Composio's team needed three things from the browser layer.

  • Volume. Browser Tool is a service for all of Composio's customers, so tasks run in parallel in isolated cloud browsers rather than one at a time on a shared machine.
  • Sites that fight back. Bot detection and CAPTCHAs are the normal case on the sites their customers care about. They needed those handled inside the session, not surfaced to the user as a failure.
  • Logins that stay logged in. Browser Tool keeps login state and cookies between tasks. Each Composio customer's sessions run on their own Browser Use browser profile, so a user signs in once and the next task on that site starts already authenticated, without the credentials passing through the agent again.

Try Browser Tool in the Composio catalog.

Published