unicli-browser

## When to Use Use `unicli browser` for browser lifecycle, page interaction, session sharing, target handoff, and diagnostics. `unicli operate` is a compatibility alias for the page-action subset. ## Provider Decision | Requirement | Provider and visibility | | -------------------------------------------- | ------------------------------ | | No window; default automation | `managed` + `hidden` (default) | | Existing signed-in Chrome tab, no activation | `chrome` + `background` | | Explicit user-visible Chrome interaction | `chrome` + `foreground` | | Explicit cloud/browser service | `remote` + `hidden` | No provider falls back to another. Managed and remote providers cannot become foreground. Existing Chrome cannot promise hidden operation. ## Quick Start ```bash unicli browser doctor --json # Probe only; starts nothing unicli browser broker start # Start windowless control plane only unicli browser start # Lazily start default managed hidden target unicli browser open https://example.com unicli browser state unicli browser click <ref> unicli browser screenshot ./page.png unicli browser sessions --json ``` ## Agent Sessions and Reuse A stable Agent session owns targets across turns. Different Agent sessions use different targets, while a shared profile partition can reuse login/storage. ```bash unicli browser --session thread-...