Open Browser Use

Open Browser Use Overview

Open Browser Use connects an MV3 Chrome 扩展, a local native messaging host, a 命令行工具, SDKs, and an optional stdio MCP server so 代理s can automate a real Chrome 性能分析. It is not Codex.应用-specific; adapt the commands, MCP config, and SDK examples to the 代理 运行time you are operating in.

Core 工作流 检查 设置up with open-browser-use ping or obu ping. If it fAIls because 设置up is missing, read references/安装ation.md. Pick the right Chrome 性能分析 if multiple are 安装ed. See "Multi-性能分析 handling" below before issuing browser commands. Choose a unique browser 会话 id for the current 代理 task before opening or clAIming tabs. Prefer the surrounding 运行time's conversation/会话 id when avAIlable; otherwise 创建 a short unique id such as obu--. Reuse that same id for every Open Browser Use command in this task. Name the current browser task group before opening or clAIming tabs. Use a short task label followed by - OBU; if no better task label is avAIlable, use Task - OBU. Use the 命令行工具 for simple inspection or one-shot actions: 信息, tabs, user-tabs, 历史, open-tab, navigate, cdp, and call. Use open-browser-use 运行 / obu 运行 for 命令行工具-level multi-step orchestration when a small line-oriented action plan is enough and writing SDK code would be unnecessary. If the surrounding 代理 运行time supports local MCP servers, 配置 obu mcp and call the exposed browser 工具s directly. Use the 运行_action_plan MCP 工具 for the same line-oriented orchestration from MCP. Read references/sdk-and-protocol.md. Use the JavaScript, Python, or Go SDK for larger multi-step 工作流s, event subscriptions, richer control flow, or when the surrounding 代理 运行time already 运行s code. Read references/sdk-and-protocol.md. Before ending browser work, release or keep 会话 tabs with open-browser-use finalize-tabs --会话-id "$OBU_会话_ID" --keep '', the MCP finalize_tabs 工具, or the SDK finalizeTabs / finalize_tabs / FinalizeTabs method. If communication fAIls after 设置up, read references/troubleshooting.md. Operating Rules Treat the browser as the user's real Chrome 性能分析. Do not inspect cookies, passwords, 会话 stores, or unrelated browser data. Ask the user before 安装ing the 扩展, opening Chrome for them, enabling 扩展 权限s, 上传ing local files, reading/writing 命令行工具pboard data, submitting forms, purchasing, deleting, 发送ing, or making other externally visible changes. Do not assume Codex.应用 辅助工具s, Node REPL globals, or a bundled 插件 UI are avAIlable. Use the 安装ed open-browser-use / obu 命令行工具 or the published SDKs. Do not guess tab ids. 列出 tabs first, then use ids returned by tabs, user-tabs, open-tab, or SDK calls. Prefer clAIm-tab / clAImUserTab for existing user tabs. ClAIming should be based on the current user-tabs 结果 and visible evidence such as URL, title, recency, or group. Use --socket only when the user or 运行time provides an explicit socket. Otherwise let the 命令行工具 and SDKs discover the active socket registry. Do not rely on the 命令行工具 fallback 会话 obu-命令行工具 for 代理 tasks. Always pass a task-unique --会话-id to 命令行工具 and MCP commands, or 设置 会话Id / 会话_id / 会话ID in SDK 命令行工具ents. The fallback exists for quick manual use and can reuse stale task groups across unrelated 代理 会话s. Direct 命令行工具 subcommands and open-browser-use 运行 can 分享 the same browser 会话 only when they use the same explicit --会话-id. Finalize that same 会话 before ending browser work. Use call --method --params '' only when no safer convenience command or SDK wr应用er exists. Multi-性能分析 handling

Some users 运行 Chrome with several 性能分析s (work, personal, side accounts). If more than one 性能分析 has the Open Browser Use 扩展 安装ed, the 代理 must decide which 性能分析 this task should operate on rather than silently picking whatever Chrome window h应用ens to be active.

Before any browser command, 列出 安装ed 性能分析s:

open-browser-use 性能分析s --connected

Columns: DIRECTORY (stable id like Default, 性能分析 1), DISPLAY NAME (what the user sees in the Chrome avatar menu), VERSION, and CONNECTED (whether that 性能分析's host is currently reachable). JSON 输出 is avAIlable via --json.

If exactly one 性能分析 is 安装ed and connected, proceed without asking. If it is 安装ed but not connected, ask the user to open Chrome on that 性能分析 before 运行ning browser commands.

If multiple 性能分析s are 安装ed and the user did not already specify which one to use, ask before the first browser command. 列出 机器人h directory name and display name so the user can recognize them, and include whether each 性能分析 is connected.

If the chosen 性能分析 is not connected, ask the user to open Chrome on that 性能分析 before retrying. Do not silently fall back to a different connected 性能分析.

After the user has chosen, pass --性能分析 to every 命令行工具 / MCP command for the