Skip to content
clutchbox

Works with

Clutchbox syncs the sign-ins from your Chrome to the browser your agent uses. Use our hosted computers with the agents you already have, or apply your sign-ins to your own browsers with the open-source adapters.

Agents

Connect these to a hosted computer, already signed in, through our remote MCP server.

Browser frameworks

Apply your synced sign-ins to a browser your own code runs, with the open-source adapters.

  • Playwright

    The Playwright adapter applies your sign-ins to a browser context, a persistent context, or a Chrome attached over CDP.

  • browser-use

    Apply your sign-ins to a Chrome started with remote debugging, then give browser-use its CDP URL.

  • Stagehand

    Apply your sign-ins to a local Chrome over CDP, then point Stagehand at the same browser.

  • Any Chrome over CDP

    The apply runtime works from a raw Chrome DevTools Protocol connection, without Playwright.

Computer and browser providers

Keep cloud computers and browsers on these providers signed in to your sites.

  • E2B

    Our hosted computers are E2B desktop sandboxes, and the open-source E2B adapter runs them on your own E2B account.

  • DaytonaPlanned

    Apply your sign-ins to Daytona sandboxes.

  • BrowserbasePlanned

    Apply your sign-ins to Browserbase sessions, without signing in again inside them.

  • KernelPlanned

    Apply your sign-ins to Kernel browsers, without storing passwords.

Using the adapters

The adapters, the apply runtime and the whole web app are open source under Apache-2.0. The repository shows how to apply your sign-ins with each. Using them with our hosted service comes with developer plans. Get notified, or ask for an integration.