Abstract
Architectures for agentic operations often involve a coupling of the input interface and the execution environment on a single piece of hardware. Such configurations can result in resource strain on mobile hardware, affecting battery longevity and data usage, and may encounter compatibility issues with desktop-centric web workflows. A dispatch protocol is disclosed that decouples the input interface from the execution environment. A dispatch payload is generated on a source device (e.g., a smartphone) or relayed via a third-party messaging channel (e.g., enterprise communication platforms or instant messaging applications). This payload includes a task prompt, browser configurations, and user context. The payload is transmitted to a target device identified through a device graph. A signal initiates a browser process and an agentic session on the target device, allowing the agent to utilize local hardware, stored authentication tokens, and local file systems to maintain data sovereignty. The protocol supports bidirectional communication, enabling real-time status updates and user "nudging" to resolve task bottlenecks. This method facilitates the asynchronous delegation of tasks within a user ecosystem based on hardware states or user-preferred communication channels.
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.
Recommended Citation
Liu, Yijo; Walsh, Shadia; Duraiswami, Lily; Shin, Yeun Su; Morris, Tiffany Deonne; Borg, Carl Magnus; Krishna, Golden Gopal; and Chan, Clifford Tse Yan, "Remote Dispatch and Initiation of Client-Side Agentic Tasks via Cross-Device Control Protocol", Technical Disclosure Commons, ()
https://www.tdcommons.org/dpubs_series/10076