How does the browser get into the right account?
Website authentication crosses several boundaries: the user who authorizes access, the system that holds credentials, the browser that submits them, and any model or code driving the page. Reusing a login and collecting a new identity are separate workflows.
For a customer-facing app, associate each stored connection with the correct application user before opening a browser. Reusing another user's profile can produce a technically successful run in the wrong account.
Compare the login path
Kernel: Managed Auth handles website login and eligible connection recovery. Vault fill is a separate flow for applications that control navigation and form submission; the reviewed vault documentation labels that surface as preview.
Anchor Browser: Applications define the target website and authentication behavior. Identities attach managed sign-in to sessions. OmniConnect supplies an embeddable flow for end users to sign in from a product.
Compare saved state
Kernel: Profiles preserve browser user-data-directory state, including cookies, site data, tabs and preferences. Profile sharing and save behavior need explicit treatment when parallel workers use seeded state.
Anchor Browser: Anchor documents browser profiles alongside an Applications and Identities model. A profile retains state; an identity supplies a managed sign-in connection used with browser sessions.
Compare the evidence from a run
Kernel: Live browser URLs support an embedded view and a read-only option. Replays and browser telemetry are separate observability surfaces; app invocation logs add execution context.
Anchor Browser: Anchor documents MP4 session recordings and a live browser used during demonstrations. Keep the session artifact alongside the task's version, inputs and completion result.
How to evaluate this choice
Compare the concrete login path. A vault can fill a secret while your code controls the workflow; a managed connection may own more of the login process. Neither should be described as a universal guarantee that every website remains signed in.
- Identify whether the task uses an existing account or creates an approved new identity.
- Separate profile restoration from credential fill and connection readiness.
- Document which component can access credential values and which only handles references.
- Verify the expected tenant and account after login.
- Provide a human handoff when the website requires user interaction.
Requirements side by side
| Requirement | Kernel | Anchor Browser |
|---|---|---|
| Saved browser state | Documented | Documented |
| Credential handling | Vaults (preview) | Managed identities |
| Website sign-in | Documented | Documented |
Sources: kernel.sh [1] ↗kernel.sh [2] ↗kernel.sh [3] ↗kernel.sh [4] ↗kernel.sh [5] ↗kernel.sh [6] ↗docs.anchorbrowser.io [7] ↗docs.anchorbrowser.io [8] ↗docs.anchorbrowser.io [9] ↗docs.anchorbrowser.io [10] ↗docs.anchorbrowser.io [11] ↗docs.anchorbrowser.io [12] ↗
Which approach fits?
Choose Kernel when your code makes many browser calls and you want to deploy it beside the browser, or you need Kernel's managed sign-in flow.
Kernel tradeoff: Browser-local code changes the deployment model. Check app action behavior, account limits and persistent-state ownership before moving an external worker into it.
Choose Anchor Browser when you want managed sign-in and an automation task you can demonstrate, edit and invoke from your application.
Anchor Browser tradeoff: A demonstrated automation task and an arbitrary Python handler are different authoring models. Evaluate how much control you need over the code, dependencies and exact workflow.
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.
When Notte belongs on this shortlist
Kernel's browser-local Apps make execution placement part of the decision. Compare the repeated action path with the proposed Notte controller or Function deployment before concluding that a lifecycle or hourly-rate difference decides the workflow.
Anchor's demonstration or prompt-authored Automation Tasks and Notte's Python Functions suit different authoring preferences. Both document website-authentication tooling, so a credible recommendation must address the actual login and workflow-editing 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.
Consider this third option when its documented mechanism addresses a requirement left open by the two providers above. A working configuration on either original provider can still be the better choice; compare the task and ownership cost before switching.
Sources: kernel.sh [1] ↗docs.anchorbrowser.io [2] ↗docs.notte.cc [3] ↗