From f6ef59ef96fdce0571e1b6dd0580a5499615fd52 Mon Sep 17 00:00:00 2001 From: walker1211 <13750528578@163.com> Date: Mon, 20 Apr 2026 21:14:13 +0800 Subject: [PATCH] =?UTF-8?q?docs(browser):=20=E5=A2=9E=E8=A1=A5=2011E=20?= =?UTF-8?q?=E8=B7=A8=20page=20orchestration=20=E8=AF=B4=E6=98=8E?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 同步 Browser MCP 文档中的显式跨页 block、run 边界与失败定位说明。 Co-Authored-By: Claude Opus 4.7 --- docs/browser-automation.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/browser-automation.md b/docs/browser-automation.md index a11285ff..8c9afe4f 100644 --- a/docs/browser-automation.md +++ b/docs/browser-automation.md @@ -147,6 +147,13 @@ Phase 11D capability details: - artifact files carry `kind`, `version`, `name`, and `payload` - cloud sync, sharing, and complex template management remain out of scope +Phase 11E capability details: + +- `open_page_then_run`, `select_page_then_run`, and `close_page_then_continue` add explicit cross-page orchestration blocks +- cross-page blocks reuse existing page/tab lifecycle control and existing single-page block semantics +- `run` accepts a normal single-page block or a single-layer `sequence` +- nested cross-page blocks, implicit page selection, and page-graph orchestration remain out of scope + Minimal multi-tab workflow examples: ```json