From d0e6087126fdd9b5a0915229a2c6fd5395e9495c Mon Sep 17 00:00:00 2001 From: walker1211 <13750528578@163.com> Date: Mon, 20 Apr 2026 19:45:47 +0800 Subject: [PATCH] =?UTF-8?q?docs(browser):=20=E5=A2=9E=E8=A1=A5=2011C=20?= =?UTF-8?q?=E6=89=A7=E8=A1=8C=E7=AD=96=E7=95=A5=E8=83=BD=E5=8A=9B=E8=AF=B4?= =?UTF-8?q?=E6=98=8E?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 同步 Browser MCP 文档中的 continueOnError、失败汇总与最小执行策略边界说明。 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 6e7a4f99..f9366389 100644 --- a/docs/browser-automation.md +++ b/docs/browser-automation.md @@ -132,6 +132,13 @@ Phase 11B capability details: - nested sequence blocks remain out of scope - sequence failures can report both top-level block failure and sequence-local step failure +Phase 11C capability details: + +- blocks and sequence steps can opt into `continueOnError: true` +- orchestration can continue after selected failures instead of always failing fast +- final results now include a lightweight `failures[]` summary and failed counts +- 11C intentionally stops short of retry, timeout override, severity, and other larger policy systems + Minimal multi-tab workflow examples: ```json