diff options
Diffstat (limited to 'FORK.md')
| -rw-r--r-- | FORK.md | 10 |
1 files changed, 8 insertions, 2 deletions
@@ -86,8 +86,14 @@ the variable is set, `/browser-target` says so instead of pretending to obey. Upstream's `BU_CDP_WS` sits above all of these: `discoverEndpoint()` returns it before consulting the fork's target, so an explicit WebSocket URL still wins. -`/browser-status`, `/browser-target` and the system prompt do not know about it, -and describe the `BU_CDP_HTTP`/stored/default target even when it is set. +`resolveCdpTarget()` mirrors that, so `/browser-status` and the system prompt +name the pinned endpoint and `/browser-target` warns that it takes precedence, +as it does for `BU_CDP_HTTP`. They show only its host:port: the path carries the +browser id, and a proxied URL may carry a token. `/browser-status` does not +probe a pinned URL, because `/json/version` answering says nothing about whether +the pinned browser id is still current. A pinned URL counts as a remote target, +like any `BU_CDP_HTTP` value, so profile selection is refused while it is set, +even for a loopback URL. The asymmetry is deliberate. An explicit endpoint is an instruction, so failing to reach it must not quietly automate a different browser — that would drive |