Event emitted when an actionable command requires host-app handling.
open:resource is always emitted. compose:email is emitted ONLY as a fallback, when the draft is too long for a mailto: URL and the host must open the draft artifact instead; a draft within the limit is handled here and never reaches the host. On that fallback the host also owns telling the user why their mail client did not open, because only the host knows whether a draft artifact opened (see ActionableCommandRequest.DraftCopiedToClipboard). open:url is always handled here.
Event emitted when an automatic command should be executed Host application should subscribe to this and handle the command appropriately
Optionalorigin: Omit<ActionableCommandRequest, "command">Execute an actionable command (triggered by user clicking a button). Generic commands like open:url are handled directly; others are emitted to the host.
Optionalorigin: Omit<ActionableCommandRequest, "command">Execute an automatic command (runs immediately without user interaction) Special handling: refresh:data commands execute locally, others emit to host
Execute all automatic commands from an agent result
Service for handling UI commands from agents.
Generic commands (open:url, and compose:email while it fits in a mailto: URL) are handled directly by this service. App-specific commands (open:resource, and the compose:email over-length fallback) are emitted for the host application to handle.