What survives between two browser sessions?
A profile is saved browser state. A reconnectable session is a browser that is still running. A managed authentication connection can establish or verify a login. These mechanisms preserve different things and need separate tests.
A restored cookie can still refer to an expired website session. The success check should inspect the signed-in account and a protected page, rather than treating a successful profile API response as proof of login.
Compare saved state
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.
AWS AgentCore Browser: The Browser Tool documentation describes ephemeral sessions that reset after use. State that must outlive a session needs an explicit storage or authentication design rather than an assumption of permanent browser state.
Compare the login path
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.
AWS AgentCore Browser: AWS credentials and IAM control access to the Browser Tool. Website login remains a separate concern: the identity used to authorize an AWS API call does not automatically sign the browser in to a third-party application.
Compare the browser lifecycle
Notte: Create an owned browser session, connect Playwright or Puppeteer over CDP, and stop the session when the work finishes. Browser lifecycle management remains necessary even when the control socket disconnects.
AWS AgentCore Browser: Create or select a Browser Tool, then start an isolated browser session. The documented default session timeout is 15 minutes and the maximum is eight hours. Browser automation uses the session's WebSocket endpoints.
How to evaluate this choice
Choose saved profiles for repeatable state restoration, a live session for work that must continue in the same browser, and managed authentication when readiness needs more than loading cookies.
- List the exact stores the workflow needs: cookies, local storage, other site data or open pages.
- Save state explicitly using the selected provider's profile contract.
- Start a second session and verify the expected account on the website.
- Test expiry and concurrent writers instead of assuming state can be shared freely.
- Keep downloaded files separate from browser login state.
Requirements side by side
| Requirement | Notte | AWS AgentCore Browser |
|---|---|---|
| Saved browser state | Documented | Explicit state design |
| Credential handling | Documented | AWS / application composition |
| Website sign-in | Documented | Separate identity design |
Sources: docs.notte.cc [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗docs.notte.cc [4] ↗docs.notte.cc [5] ↗docs.notte.cc [6] ↗docs.aws.amazon.com [7] ↗
Which approach fits?
Choose Notte when your browser workflow needs saved logins, credential fill or scheduled Python code alongside the browser.
Notte tradeoff: A saved profile restores browser state; it does not prove that a website still considers the user signed in. Use Managed Auth when the workflow needs connection readiness before it starts.
Choose AWS AgentCore Browser when your application already uses AWS identity, logging and storage, and browser workflows need to fit those systems.
AWS AgentCore Browser tradeoff: The browser tool is not the entire AgentCore platform. Do not assign capabilities from unrelated AgentCore execution or identity products to a browser session without specifying the composition.
A useful acceptance check
Write a pass/fail result for the real task before running the evaluation. Record the account, configuration and code version next to that result. Repeat failures need an explanation, not an automatically different browser configuration.