PDPP

Retire Browser Daemon

in progresstasks29/32retire-browser-daemon
openspec/changes/retire-browser-daemon/View on GitHub →

Artifacts

Official change artifacts tracked under openspec/.

Proposal

The polyfill connector subsystem has two browser-launch paths that no production runtime uses:

Design

The daemon's pitch was: long-lived Chromium preserves Session-scoped cookies (no Max-Age) across connector runs, so banking sites with short server-side sessions don't force a re-auth on every run.

Tasks (29/32)
Spec Deltas (1)

Affected capabilities

Capability specs this change proposes to modify.

Polyfill Runtime

The polyfill-connector runtime SHALL provide exactly one browser-launch primitive (acquireIsolatedBrowser) that launches a per-connector patchright Chromium with an isolated profile directory. Browser-backed connectors and operator tools SHALL NOT use a long-lived shared Chromium daemon, CDP-attach, or a shared profile directory across connectors.

polyfill-runtime

Project notes

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

Retire Browser Daemon

1 notes · 1 working note · updated

Working notes
Browser-channel decision memo

---

created