Decide whether this move earns its cost
A controller loses its connection midway through a safe task and attempts to continue. Starting a fresh browser is not always equivalent to reconnecting to a live page.
Browser Use's hosted-agent offering and standalone browser infrastructure are separate options. Keep the comparison at the browser layer when your application already owns its controller; compare execution ownership separately if the hosted agent is part of the requirement.
Evaluate Notte when browser ownership can be tracked independently of a transient controller socket. Confirm the supported reconnection path and distinguish it from loading a saved profile.
A provider's documented reconnect product can be decisive for a workflow that depends on a live page. Do not replace it with profile persistence without changing the task's continuation design.
Keep the result contract stable
A page with unsaved in-memory state, a stored provider session reference and a controlled controller interruption.
The application determines whether the original browser is still alive and either resumes the expected state or explicitly restarts the task.
Preserve the evidence contract across the move: Original session reference, page-state marker, connection interruption and resume-or-restart decision.
Map the workflow's resources
| Requirement | Browser Use | Notte |
|---|---|---|
| Browser control | Documented | Documented |
| Saved browser state | Documented | Documented |
| Live view | Documented | Documented |
| Deployment choice | Local framework available | Enterprise options |
Sources: docs.browser-use.com [1] ↗docs.browser-use.com [2] ↗docs.browser-use.com [3] ↗docs.notte.cc [4] ↗docs.notte.cc [5] ↗docs.notte.cc [6] ↗docs.notte.cc [7] ↗
What survives a session
Browser Use: Profiles persist cookies, local storage and login state between browsers. Browser settings select a profile for a run. A session's conversation history and a profile's browser state are different resources.
Notte: Profiles save cookies, local storage and session storage. Sessions start with fresh state by default. Persisting a profile writes state back when the session ends; a running session can also save its state explicitly.
Website login
Browser Use: V4 secret bindings give credentials aliases and allowed hostnames for use in a run. Profiles reuse existing state; the separate 2FA guide addresses verification during authenticated work.
Notte: Vaults substitute credential placeholders in supported browser actions outside the model context. Managed Auth checks requested saved connections before automation. Personas supply an inbox and optional phone number for verification workflows.
Deployment ownership
Browser Use: Use the hosted browser from your own process or send a task to the hosted agent. The open-source local framework is another deployment option and should not be equated with the cloud subscription.
Notte: Use a remote browser from your existing process or deploy the browser automation as a Notte Function. These choices put lifecycle, scheduling and monitoring responsibilities in different places.
Pricing model
Browser Use: Browser time and hosted-agent/model usage are separate pricing questions. Select the infrastructure path before comparing rates, and account for retained idle browser time and network usage where applicable.
Notte: The public usage rates are $0.01 per browser-hour, $0.05 per Function-hour and $10 per GB of managed proxy traffic. Paid plans return their price as usage credits. Price the relevant meters and plan eligibility for the workload.
Cut over one responsibility at a time
For this Browser Use-to-Notte migration, keep the business assertion outside provider resource management. Source profile, connection, file and execution IDs are not valid target IDs; use a documented transfer path or establish the corresponding resource in Notte.
Retain source job history and a rollback route until the target pilot passes. A migration checklist is not evidence that saved state or runtime behavior is automatically portable.
- Inventory which steps depend on unsaved page state.
- Test the target session's documented connection path before moving continuation logic.
- Retain a restart path for ended sessions and verify that cleanup still occurs.
Sources: docs.browser-use.com [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗
A proposed acceptance case
This is an evaluation design, not a claim that this workflow has been executed successfully on every provider.
| Part of the test | Required observation |
|---|---|
| Controlled input | A page with unsaved in-memory state, a stored provider session reference and a controlled controller interruption. |
| Pass condition | The application determines whether the original browser is still alive and either resumes the expected state or explicitly restarts the task. |
| Negative case | Repeat the reconnect after the browser has ended. The application must not treat a new session or restored profile as the original live page. |
| Evidence to retain | Original session reference, page-state marker, connection interruption and resume-or-restart decision. |
A reason to delay or keep the source
Repeat the reconnect after the browser has ended. The application must not treat a new session or restored profile as the original live page.
Browser Use: A hosted-agent run is a different execution unit from your deployed browser script. Keep comparisons focused on the browser path when measuring session speed and price.
Delay cutover when the target's selected plan, required artifact path or supported website-account flow is not established. Resolve that gap before moving real jobs, even if the rate comparison favors the target.