Chrome Profile Debug

Chrome Profile Debug exposes one Chrome profile to a local automation host, under a name you choose, so developer tooling on the same machine can drive that profile. Chrome keeps every profile in a single browser process. Tools that attach over --remote-debugging-port therefore see all of your open profiles at once and cannot tell them apart, and they do it through an unauthenticated port on localhost that any local process can reach. Extension-based tools usually bind to whichever single profile happens to be paired, leaving you unsure which one an automation actually touched. This extension takes a different approach. You name each profile once. Every command from your tooling names the profile it is for, so there is never any doubt about which browser session was driven. HOW IT WORKS The extension talks to a companion program on your own computer through Chrome's native messaging API. That program is open source and you install it yourself. No TCP port is opened. The extension has no network capability of its own and no host permissions, so it never injects a content script into any page and has no passive presence on the sites you browse. Page interaction goes exclusively through the Chrome DevTools Protocol, which means Chrome displays its debugging banner on any tab being driven. The extension never suppresses that banner. OPT-IN, PER PROFILE A profile with no name never connects. Installing the extension in a profile does nothing on its own; you have to open the popup and name it. Clearing the name disconnects it again. WHAT YOU NEED The companion host requires Node.js 20 or later and a one-time setup step. The Chrome Web Store cannot install it for you. Source, installation instructions and the full security model: https://github.com/marcondesmacaneiro/chrome-profile-debug PRIVACY No analytics. No crash reporting. No usage telemetry. No server operated by the author. Page content read on your instruction is relayed only to the local program you connected.