Where does the browser automation code run?
An external worker, a hosted browser Function, a browser-local app action and a hosted agent are different execution models. The choice determines who deploys the code, starts the browser, records the result and stops the run.
A scheduled job should return a verified result and stop its owned browser even when an action fails. The scheduler's successful HTTP trigger is not proof that the browser completed the business operation.
Compare the execution model
Browserbase: A Function is TypeScript code published with an entry point. Invocation starts asynchronously, creates a browser, passes its connection URL to the handler, and stores the result, logs and session ID. Function webhooks report status changes.
AWS AgentCore Browser: The Browser Tool supplies the browser environment. An external process or another AWS execution service runs the application code that controls it. Identify that service and its runtime before comparing it with a deployed browser Function.
Sources: docs.browserbase.com [1] ↗docs.aws.amazon.com [2] ↗
Compare deployment ownership
Browserbase: Publish TypeScript Functions through the supported deployment flow. The reviewed Function overview lists us-west-2 availability; this is narrower than assuming every browser region also hosts Functions.
AWS AgentCore Browser: Use an AWS-managed Browser Tool or configure a custom browser with recording, networking and an execution role. Keep the controller's deployment separate in the architecture and operational estimate.
Sources: docs.browserbase.com [1] ↗docs.aws.amazon.com [2] ↗
Compare the evidence from a run
Browserbase: Browserbase documents live session views, recordings and observability. Function results also include a session association, so correlate the handler outcome with the actual browser run.
AWS AgentCore Browser: Live View allows real-time browser interaction. Custom browsers support recording to your S3 bucket, with replay through the AWS Console. CloudWatch and CloudTrail provide additional operational visibility.
Sources: docs.browserbase.com [1] ↗docs.aws.amazon.com [2] ↗
How to evaluate this choice
Keep an external runner when you already operate one and need portability. A native execution layer can remove deployment work; browser-local code can reduce repeated network calls. Compare actual workload behavior before assuming either always wins.
- Confirm the supported language, entry point and dependency packaging.
- Trace deployment, version selection, invocation and cancellation.
- Keep the handler runtime limit separate from browser session duration.
- Decide whether scheduling is native or supplied by another service.
- Associate results and logs with both the code version and browser session.
Requirements side by side
| Requirement | Browserbase | AWS AgentCore Browser |
|---|---|---|
| Code execution | TypeScript Functions | External AWS compute |
| Scheduled execution | External trigger path | External scheduler |
| Recordings / replay | Documented | Custom browser + S3 |
Sources: docs.browserbase.com [1] ↗docs.browserbase.com [2] ↗docs.browserbase.com [3] ↗docs.browserbase.com [4] ↗docs.browserbase.com [5] ↗docs.aws.amazon.com [6] ↗
Which approach fits?
Choose Browserbase when you want to deploy TypeScript browser logic or already use Browserbase's browser and Stagehand tooling.
Browserbase tradeoff: An identity feature, a persisted Context and a Function secret solve different problems. Select the required combination instead of treating all three as automatic login.
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.
Sources: docs.browserbase.com [1] ↗docs.aws.amazon.com [2] ↗
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
Browserbase's TypeScript Function contract is a reason to retain it when that is the deployed language your team wants. A move to Notte Functions includes a Python execution decision; moving only the browser can leave your existing controller in place.
AgentCore Browser's AWS integration can matter more than moving a browser endpoint. Retain AWS identity and observability requirements in the evaluation, and separately account for the code runner and website login before comparing Notte's integrated workflow.
Notte: Functions deploy Python code with a run() entry point. Invoke them over HTTP or with an SDK, inspect run history, and roll back code by redeploying an earlier version as the latest version.
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: docs.browserbase.com [1] ↗docs.aws.amazon.com [2] ↗docs.notte.cc [3] ↗