How to use chrome-faithful
Control your real, logged-in Chrome profiles over MCP: exact multi-profile routing through an MV3 chrome.debugger extension and an authenticated localhost bridge. No copied profiles, no debug profile, no remote-debugging port, no Edge. Includes multi-signal challenge detection with humanized verification handling, page File injection, signed-URL-safe media export, and durable virtual-list capture.
This article is auto-derived from indexed fields (wiki / faq / compatibility_json), not freshly AI-generated.
This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.
Quick start
Control your real, logged-in Chrome profiles over MCP: exact multi-profile routing through an MV3 chrome.debugger extension and an authenticated localhost bridge. No copied profiles, no debug profile, no remote-debugging port, no Edge. Includes multi-signal challenge detection with humanized verification handling, page File injection, signed-URL-safe media export, and durable virtual-list capture.
— source: plugins.ai_summary
Install & verify
dsh plugin --profile web add github:bpc-oss/chrome-faithful
Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.
— source: plugins.install
Pitfalls
Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.
— source: general rule