# Browser And Desktop - Canonical: https://olo-dot-io.github.io/Uni-CLI/guide/browser-desktop - Markdown: https://olo-dot-io.github.io/Uni-CLI/markdown/guide/browser-desktop.md - Section: Use Uni-CLI - Parent: Use Uni-CLI (/guide/) Uni-CLI groups browser and desktop actions under stable command families. Start with a state read, select a concrete target, then perform the action. ## Browser sessions Check the local setup: ```bash unicli browser doctor --json ``` Start a hidden managed browser: ```bash unicli browser start ``` Use an existing Chrome session in the background: ```bash unicli browser --background start ``` Open a page and inspect its accessible state: ```bash unicli browser open https://example.com unicli browser state -f json ``` The state response assigns refs to interactive elements. Pass a ref to actions such as `click`, `type`, and `query`. ```bash unicli browser click unicli browser type "search text" ``` ## Desktop applications Search by the result you want: ```bash unicli search "inspect a desktop application" --surface desktop ``` Read compute health before the first desktop session: ```bash unicli doctor compute -f json ``` Take a snapshot, then act on a returned ref: ```bash unicli compute snapshot --app "Calculator" -f json unicli compute click --app "Calculator" -f json ``` Available providers depend on the operating system and installed accessibility services. The health response lists the active provider and the setup action for each unavailable provider. ## Choose the smallest useful interface Structured APIs and native CLIs are efficient for data and repeatable actions. Browser semantics are useful for signed-in pages. Desktop accessibility reaches installed applications. Visual actions cover interfaces that expose only pixels. `unicli search` reports the operator selected by each catalog entry.