n8n 2.43 expands Browser Use in its AI Assistant

With n8n 2.43, released October 6, 2026, the vendor documents a wider rollout of Browser Use in its AI Assistant. The feature is no longer limited to an experiment and is described as available to all users in the supported environment. That is an Assistant browser-control feature; it does not automatically mean every n8n AI Agent node has acquired autonomous browser access or that every workflow can control websites without configuration.

What changed exactly?

Availability remains subject to an instance-level setting, N8N_INSTANCE_AI_BROWSER_USE_ENABLED. The release notes say it is enabled by default but an administrator can disable it. Organizations using managed environments or self-hosted deployments must therefore confirm the installed version, instance policy and whether the feature is actually enabled before depending on it.

The mobile limitation is unusually explicit: n8n says Browser Use remains unavailable on phones and tablets, including iPads operating in desktop mode. Users should not read the phrase 'available to all users' as a claim that every device, region or deployment configuration is supported. A desktop test in the actual deployment is necessary.

Who benefits and what remains uncertain?

In practice, browser-assisted work can be helpful for bounded interactions with web interfaces, but control of a browser is different from permission to make purchases, send messages or modify production records. Tool credentials, network exposure and approvals remain independent responsibilities. Test on non-sensitive pages and give the assistant only the access needed for the specific job.

For teams, a careful rollout should begin with reproducible tasks, logging of browser actions, clear human approval points and a fallback for unexpected page changes. The full release also discusses migration reports and Agent Builder changes, but this article deliberately limits its capability claims to Browser Use within the n8n Assistant. It does not promise that arbitrary agents will become faster or more reliable.

The AgentenCode n8n Agents profile provides background on n8n automations and agent workflows. The Browser Use rollout must not be transposed automatically to every agent configured in the platform. Our evidence is the official n8n release note and related source repository change; AgentenCode has not independently benchmarked the feature.

Frequently asked questions

Can I use n8n Browser Use on an iPad?

No. n8n explicitly says the feature is unavailable on phones and tablets, including iPads in desktop mode.

Does every n8n instance have Browser Use enabled?

The documented admin setting defaults to enabled but can be switched off. Check your version and actual instance configuration.