It sounds like you're thinking of window.navigator.webdriver, which is a WebDriver thing not part of Chrome DevTools Protocol. With CDP, as far as I can tell the detection mechanisms are more about the heuristics of e.g. how fast a form is filled -- which this AI stuff will trigger immediately too.
(And even if CDP had an explicit marker somewhere, surely patching that out is easier than piling up enough patches to "make a new browser".)
Tsarp
Dont you need to navigator.webdriver === true for CDP to drive automation? Maybe I need to update my understanding on this. THis is usually a dead giveaway
yencabulatorOP
I see mentions that (unpatched) webdriver is easy to detect but detecting CDP only works by heuristics on timing etc.
(And even if CDP had an explicit marker somewhere, surely patching that out is easier than piling up enough patches to "make a new browser".)