n8n's Browser Use ships on by default: check this first

Browser Use, n8n's built-in tool for letting an AI agent control a web browser, is now on by default for every workflow on your instance. The change shipped in n8n 2.43 on October 6, replacing the older experimental flag with an instance-wide setting that ships turned on.

That means if you or anyone on your team built a workflow with an AI Agent node any time in the last year, that agent can now reach for a real browser session and start clicking, typing, and submitting forms on its own, using whatever login or credentials that session already has. Nothing forces you to opt in. The feature arrived active.

What Browser Use actually lets an agent do

Under the hood, Browser Use gives an agent a set of interaction tools: it can click elements, type into fields, scroll the page, and upload files, with an optional accessibility snapshot sent back so the agent can see what it is working with. It will not run on a phone or tablet browser, including an iPad in desktop mode, but on a desktop session tied to an n8n instance, it behaves like a person sitting at the keyboard. The one setting that controls all of this instance-wide is N8N_INSTANCE_AI_BROWSER_USE_ENABLED, and n8n ships it set to true.

Why that is worth a second look

• Any workflow with an AI Agent node can now add a browser tool without an admin turning anything on first.
• The browser session uses whatever credentials or logged-in cookies are already available to it, not a separate, scoped login.
• There is no per-workflow permission layer yet. The control lives at the instance level, on or off for everyone.
• The automatic credential setup option that used to accompany this feature is now disabled by default, which n8n frames as a safety step, but the browser control itself is not.

What to actually do about it

1. 1

   Confirm your version

   Check whether your instance is on 2.43 or later. If you self-host, this is in your admin panel. If someone else hosts it for you, ask them.

2. 2

   Find the setting

   Look for N8N_INSTANCE_AI_BROWSER_USE_ENABLED in your environment variables or instance settings, and confirm whether it is on.

3. 3

   Audit your AI Agent workflows

   Open every workflow that uses an AI Agent node and check whether a browser tool is attached, even one you don't remember adding.

4. 4

   Decide a default posture

   Turn it off instance-wide until you have a specific workflow that needs it, then enable it only where you have reviewed what credentials that session can reach.

None of this means Browser Use is a bad idea. Letting an agent click through a site it can't otherwise reach by API is genuinely useful for some workflows. It just means the default changed under you on October 6, and it is worth five minutes to check what your instance is actually set to before an agent goes looking for a browser to open. If you want a second pair of eyes on which of your workflows should have that kind of access, that's worth talking through.