browser-use-operator

To automate browser tasks with session continuity, use named session management to open, reuse, and close persistent browser sessions. This maintains cookies and authentication state across multiple automation steps without requiring repeated logins.

For manual login handoff during headed browsing, run a headed session to allow visual login confirmation, then resume the automated session. This lets users complete authentication manually before the workflow continues interacting with the page.

To interact with specific page elements reliably, read structured JSON page state before and after actions to identify indexed elements. Then apply deterministic click, input, upload, or eval actions based on the inspected state rather than guessing element indices.

The best way to troubleshoot failing interactions on real websites is to prefer direct URL opens, re-check page state after transitions, and use eval actions to discover hidden links or interact with custom editors during site-specific debugging.

Yes, you can perform file uploads through automated browser workflows using deterministic upload actions. The state-first workflow reads interactive page state to identify upload elements, then applies the upload action to complete reliable file submissions.

Yes, you need to source the shell profile to expose the browser-use binary on your local machine. This ensures the local CLI is available in the environment to execute real browser interactions and maintain named sessions.