Using a remote chromium via a ws_url requires a local chromium binary

[wgwz]

I'm probably missing a key reason that this is required.
But why is that I have to have a locally installed chromium binary if I'm operating a remote chrome via ws_url?
That was surprising at first when I saw it.
But perhaps that should not be surprising at all!
Curious at a minimum to know the answer to this question.
But perhaps there could be a documentation addition that grows out of this.