From a03c29589da009d87f7b2a8842c1acedd7358e9f Mon Sep 17 00:00:00 2001 From: mason5052 Date: Sat, 13 Jun 2026 23:04:56 -0400 Subject: [PATCH] docs: add recommendation and requested decision to BrowserOS MCP RFC --- examples/proposals/browseros_mcp_browser_backend.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/examples/proposals/browseros_mcp_browser_backend.md b/examples/proposals/browseros_mcp_browser_backend.md index 15eec305..a6a13c3a 100644 --- a/examples/proposals/browseros_mcp_browser_backend.md +++ b/examples/proposals/browseros_mcp_browser_backend.md @@ -404,4 +404,15 @@ Recommended behavior: - Keep policy failures fail-closed and do not use fallback to bypass scope or approval decisions. +## Recommendation and Requested Decision + +This RFC recommends adopting BrowserOS MCP as an optional, disabled-by-default browser backend while the scraper backend remains the default, implemented incrementally (milestones 1-3 first): + +- **Default:** the scraper stays the default backend; BrowserOS MCP is opt-in via configuration, so existing deployments are unaffected. +- **Transport and security:** bind the MCP endpoint to localhost by default and require an auth token (or mTLS) for any remote endpoint; treat the tool identifiers in this RFC as illustrative until validated against a real BrowserOS MCP server. +- **Scope for the first PR:** read-only browsing (navigation, page and link extraction, snapshots, and screenshots through the existing artifact path). State-mutating interactive actions (click, fill, submit) are deferred to a later, approval-gated milestone. +- **Isolation and audit:** per-flow session isolation, fail-closed policy checks, and audit logging of every state-mutating action. + +Decision requested from the maintainer: approve BrowserOS MCP as an optional, default-off backend with this read-only-first scope, request changes, or decline. Approval unblocks an implementation PR for the read-only backend behind a disabled-by-default flag. + Refs #342