Open Browser Use

Automate real Chrome profiles with a professional CLI, SDK, and MCP-ready automation stack for AI agents.

Install
cmdop skills install agensi-open-browser-use

Open Browser Use (OBU) is an automation framework that allows AI agents to control a real Chrome profile. This skill enables agents to interact with a user’s actual browser sessions, including saved logins, extensions, and local files. It provides multi-profile management, allowing for the detection and switching between different Chrome profiles like work or personal accounts. The skill ensures session persistence through managed task groups, which are designed to organize tabs by project and include built-in cleanup routines. Furthermore, OBU supports advanced interactions such as direct Chrome DevTools Protocol (CDP) commands, which give an agent granular control over the browser. It also allows for file chooser interception for uploads, enabling automated file submissions, as well as download monitoring to track completed downloads. Clipboard management is also supported, facilitating data transfer within automated workflows. OBU integrates with AI agent runtimes via a local Model Context Protocol (MCP) server, offering a comprehensive toolkit for sophisticated web navigation and interaction.

Use cases

  • Automate web browsing tasks using a real Chrome instance.
  • Manage multiple Chrome profiles for distinct automation tasks.
  • Control file uploads and monitor downloads within an automated browser session.
  • Utilize Chrome DevTools Protocol commands for granular browser control.
  • Maintain authenticated sessions across multiple browsing operations.
  • Integrate browser automation with AI agent runtimes via MCP.

When to use it

  • When AI agents need to interact with a real Chrome profile, not a sandboxed environment.
  • When complex, multi-tab web workflows require session persistence.
  • When agents need to handle CAPTCHAs or authentication processes.
  • When the capability to switch between different Chrome user profiles is required.
  • When fine-grained control over browser actions, such as direct CDP commands, is necessary.

When not to use it

  • If browser automation is not required.
  • If interaction with a real Chrome profile or user session data is not desired.
  • If a lightweight, headless browser environment is sufficient for basic web scraping.
  • If the local machine does not have Chrome installed or access to its profiles.
  • If an agent requires interaction with browsers other than Chrome.