1# Browser Use CLI Tested Notes
2 
3These checks were actually performed in this environment.
4 
5## Successful checks
6 
7- `uv tool install browser-use`
8- `browser-use doctor`
9- `browser-use open https://example.com`
10- `browser-use state`
11- `browser-use get title`
12- `browser-use screenshot generated/browser_use_test/chromium_example.png`
13- `browser-use --browser real open https://example.com`
14- `browser-use --browser real state`
15- `browser-use sessions`
16- `browser-use close --all`
17 
18Observed state output was consistent in both Chromium and real-browser mode:
19- page title: `Example Domain`
20- indexed clickable element visible in state output
21 
22## Important installation nuance
23 
24`browser-use install` tried to install browser/system dependencies and failed because dependency installation wanted `sudo`.
25 
26Despite that failure, the CLI still worked for local smoke tests in this environment.
27 
28Implication:
29- do not assume `browser-use install` must fully succeed before every local test
30- if local commands already work, continue
31- if a target machine is missing dependencies, expect Linux setup friction around system packages
32 
33## Not tested here
34 
35- Browser Use cloud auth with a real API key
36- Cloud tasks / cloud v2 or v3 passthrough
37- Tunnels
38- MCP stdio mode
39- Full login-reuse flows against a real authenticated site
40