screen tool lets an agent arrange the browser-based Control UI. It is a
typed layout and navigation surface, not screenshot capture or browser
automation.
The tool is exposed only when the originating client advertises the
ui-commands capability. At least one capable Control UI must still be
connected when the tool runs; otherwise the Gateway returns UNAVAILABLE.
Actions
A successful command returns
{ "ok": true } after the Gateway broadcasts
the typed ui.command event.
Routing and security
Protocol v1 intentionally sends the command to every connected Control UI that advertisesui-commands; it does not target one browser tab. This matters when
the same operator has several dashboards open.
The Gateway RPC requires operator.write. The tool can change presentation
state only: it cannot read pixels, take screenshots, click arbitrary page
content, or bypass the permissions of the selected session and operator
panels.