Command Prompts Menus are the way Document Editor is doing things via API. In the Xorg days it could sends Instructions via Network and Render OpenGL/(EGL?) as remote application locally via some xorg protocol extensions madness.
sending Streams of GPU instructions is hard, but Reactive (Streams) in HTML(and Game) world is a Reality and today also in Video Server Hosting if Data Traffic Packages allows which is weird even for Apps hostings traffic Downloads.
but Sending Instructions What to Do is framework agnostic, so even Sending Instructions as Command Prompt via API is possible to tell remote API to do something. And today it is possible to tell remote browser to do something. VIA classic browser headless API or even Chrome native Protocol to implement Command Prompt API or some chosen framework or implementation if found or programmed.
So the old way to tell remote to send GPU instructions is maybe on Wayland Protocol still needed(translation Mesa protocol? implementation if allowed like is Mesa full of them, but when IEEE, ECMA(international), IETF standards developed (even some IANA) it could industry help as even Message Posting Protocols is communications awareness ahead),
but Reactive Streams are Today HTML/… reality but as always other tech details are still hard for developers to make their jobs and solve their CV, maybe some xorg foundation grants ahead but that is consortium industry thing behind curtain.