sitabanubanu Browser Host Identity
Treat Edge and Chrome as separate hosts with separate profiles, cookies, extensions, and login state. A Chromium-compatible extension, a tool named "Chrome", a generic OpenCLI profile ID, or the system default browser is not host evidence.
- Read
references/host-identity-protocol.mdbefore any browser/session operation. - Honor an explicit user choice exactly: Chrome means Chrome only; Edge means Edge only. Never open or fall back to the other host.
- When the host is not explicit, inspect the actual visible browser or ask for the host before accessing login state, cookies, or an extension. Do not infer it from a control surface name.
- Record
browser_hostasedgeorchromeand record whether it was user-declared or directly verified. If it remains unknown, stop the browser-session route or mark the export asnot_provided. - For Knowledge Workflow OpenCLI acquisition, pass
--browser-host edgeor--browser-host chrome. The adapter blocks an OpenCLI route with no host. - For yt-dlp browser cookies, pass the same host through
--youtube-browser edge|chrome; conflicting host flags are an error. - Never read, display, copy, or persist cookie values, session IDs, tokens, passwords, or private headers.
Use an in-app browser only as its own surface; it is never evidence that an Edge or Chrome login session is available. Read the reference for conflict, verification, and handoff rules.