Expand description
The browser-bridge daemon service: hosts the bridge’s loopback-TCP planes under the daemon’s lifecycle and exposes status/control to it.
The security model is unchanged from ADR-0036 — the bridge keeps both its
TCP planes and their bearer-token auth, and the daemon never proxies browser
traffic. The only additive delta is that the resolved session token is
persisted to a 0600 file so thin clients (request/harvest) can
discover it without the foreground stdout a standalone serve prints.
Structs§
- Bridge
Service - Hosts a
BridgeServerunder the daemon, persisting its session token for thin-client discovery and allowing in-place restart.
Constants§
- SERVICE_
NAME - The browser-bridge service name (the control-socket routing key).