With Katalon 10.0.1 instead of previous latest version of katalon 9, migration doc suggest to use new chromeOptions instea dof “old” desired capabilities, yet mention to update the so called Project > Settings > Desired Capabilities in such a way that previous string list args is now child of a new goo:chromeOptions Dictionnary item. Why not but… it does not seem to work.
Does it work for you? It seems to be “compliant with W3C” thus not related specifically to Katalon 10 and maybe lots of you already migrated even on versions 9, yet I cannot find a way to make it work: with or without webSocketUrl (one of such args is incognito which is not compatible with BiDi so I need to disable it), with or without “–” before “incognito” etc…
So I finally ended up re adding args string list at the root of web UI chrome desired capaiblities and it works fine again, but maybe one day it will not any more? Anyway if there is a better / standard way of doing let us use it, but it should work. 
These project settings are the only places where we specify browser settings, nowhere else in our code or scripts, in case it helps.
Same for Edge Chromium, I tried ms:edgeChromium true and ms:edgeOptions dictionnary, but locally the version which opens is not incognito at all (with Edge seems to be inprivate or -inprivate or --inprivate I tried all but none work) and I have profile to select once browser opens which is ugly but navigating to a URL seems to skip this, and most importantly I cannot resize the browser which makes tests fail locally whereas from docker image / KRE run it is ok…
So does this way of specifying browser settings via Katalon Desired Capabilities and goo:chromeOptions or ms:edgeOptions work at all? If yes, any debug tips we can share?