PDPP

Design Host Browser Bridge For Docker

in progresstasks24/29design-host-browser-bridge-for-docker
openspec/changes/design-host-browser-bridge-for-docker/View on GitHub →

Artifacts

Official change artifacts tracked under openspec/.

Proposal

Browser-backed polyfill connectors can require human interaction: Cloudflare challenges, OTP prompts, "is this you?" confirmations, and archive-export verification steps. In a native local deployment, the headed browser appears on the owner's desktop. In Docker, the connector process can launch Chrome inside the container, but the owner cannot see or control that browser.

Design

Short-term Docker interaction support is specifically host browser control:

Tasks (24/29)
Spec Deltas (1)

Affected capabilities

Capability specs this change proposes to modify.

Reference Implementation Architecture

When the reference implementation runs browser-backed connectors inside a local Docker deployment, it SHALL NOT silently launch an inaccessible headed browser inside the container. The deployment SHALL either use an explicitly configured host-browser bridge or report that browser interaction is unavailable.

reference-implementation-architecture

Project notes

Change-local notes that support this workstream but have not been promoted into the official change artifacts.

Design Host Browser Bridge For Docker

1 notes · 1 working note · updated

Working notes
Host-Browser Bridge Feasibility Spike

Memo-only output of the feasibility slice for the design-host-browser-bridge-for-docker change. Captures what we learned about driving a visible host browser from a Dockerized connector runtime, the constraint surface that shapes the recommendation, and the smallest vertical slice we'd build first.

created updated