Chrome Login-Free Debug Browser

Problem

Domestic platforms often rely on QR-code login, CAPTCHAs, and risk-control context, making stateless browser automation or raw API calls brittle. This skill treats login as a one-time human step: a dedicated Chrome profile signs in manually, and later agents reuse the persisted cookies through Chrome DevTools Protocol.

How It Works

• Isolated profile: uses --user-data-dir to keep cookies, extensions, and history separate from the main Chrome profile.
• Debug port: launches with --remote-debugging-port=9222 and --remote-allow-origins=* for local CDP WebSocket access on Chrome 128+.
• Session reuse: after one manual login, the agent can open tabs, run JavaScript, click elements, fill forms, and read page content while staying logged in.
• Platform expansion: adding another platform only requires opening it in the debug browser and logging in once; no code or config changes are needed.

Boundaries

Best for local automation with occasional human intervention. The approach expects a real Chrome window because headless mode is more detectable. The debug port is typically bound to localhost, but any local process that can reach it can control the browser, so test accounts are safer. Cookies can expire, and migrating the profile to another machine does not guarantee that every platform will accept the session.