What is being crippled here? The ability to execute arbitrary JavaScript in content scripts at runtime. Remote-browser works by making it very easy to run code

What is being crippled here? The ability to execute arbitrary JavaScript in content scripts at runtime. Remote-browser works by making it very easy to run code in content and background script contexts from a remote client. Typical browser automation tasks like filling out an input, clicking a button, or extracting the HTML of an element are accomplished by marshaling code and results between the browser and the client. your point is that the API was stable with V2 My point isn't that the API was stable, it's that Google is moving towards removing key features from the API because they consider them to be too powerful. Blocking webRequest and executeScript are two notable examples.