What it is
A browser started with remote debugging exposes a WebSocket endpoint. Libraries such as Playwright and Puppeteer connect to it and send commands, which is how automation drives the real browser.
Why it matters
In an antidetect browser the important point is to connect to the running profile’s endpoint instead of launching a second browser, which would have a different identity.
What to do
Start the profile through the browser’s own API, read the endpoint from the reply, and connect your library to it.
In Clout Browser
Starting a profile through the Local API returns its CDP WebSocket in the reply (data.ws.puppeteer); connect Playwright with connectOverCDP and stop through the API so the session is collected.