Brave and Firefox on managed devices

How to Disable AI in Brave and Firefox on Company Devices

Chrome and Edge get the policy attention. Brave and Firefox ship their own AI: an assistant that reads the open page, an agentic browsing mode, a sidebar chatbot and AI add-ons.

On a company laptop, those features follow nobody's rules until you set policy. This page shows the policies that switch them off and how to block agent extensions in both browsers.

Brave

  • Leo assistant
  • AI browsing (agentic, opt-in)
  • Local AI features
  • Chrome Web Store extensions

Firefox

  • Sidebar AI chatbot
  • Link preview key points
  • Smart tab groups
  • AI add-ons

Next step

AI Agent Blocklist for Brave, Firefox and every other browser you allow

Agent extension IDs for Chrome, Edge and Firefox plus AI agent domains in one daily list, ready for browser policies, your firewall and your DNS filter.

From $99 a month for one organisation

What AI is built into Brave and Firefox now

Both browsers have added AI release by release. Some features are on by default, some are opt-in, and some download models to the device. Here is what an admin should know about each.

Brave
  • Leo, the AI assistant On unless set by policy

    Answers questions, summarises the open page and writes text. If no policy is set, it is available to every user.

  • AI browsing Opt-in, early testing

    An agentic mode where Leo works through websites for the user. It moved from Nightly to early testing on all release channels in May 2026, behind a flag.

  • Local AI Newer releases

    On-device AI features such as history embeddings. A newer policy hides them and stops the on-device components from installing.

  • Chrome Web Store extensions User installs

    Brave installs Chrome extensions, so agent extensions built for Chrome run in Brave with the user's logged-in sessions.

Firefox
  • AI Controls in Settings Firefox 148+

    Firefox 148, released on 24 February 2026, added an AI Controls section to Settings. Users can switch AI features on and off there unless policy locks them.

  • Sidebar chatbot User chooses provider

    A sidebar panel that connects to third-party chatbots such as ChatGPT, Claude, Gemini or Copilot, with prompts like summarise and explain.

  • Link previews and smart tab groups Firefox 144+

    AI key-point summaries inside link previews, and AI suggestions for tab group names and which tabs belong together.

  • On-device features and Smart Window Varies by version

    Translations, PDF alt text, speech recognition and Smart Window features. Blocking an on-device feature by policy also removes models already downloaded.

Why built-in browser AI is a problem on work laptops

This is not a judgement on Brave or Firefox. The issue is unmanaged AI on a device that holds company sessions, files and customer data.

Page text leaves the device

A chatbot that summarises the open tab works on that tab's text. On an internal wiki, an HR record or a CRM screen, that text is company data going to an AI service.

Agents act inside sessions

Agent extensions in the main profile can click, type and submit forms where the user is already signed in. Hidden text on a page can steer them.

The second browser gets forgotten

Teams that tune Chrome and Edge policies often leave Brave and Firefox at defaults. Users who want AI simply switch browsers.

Extensions bypass feature policies

Turning off Leo or the Firefox chatbot does nothing about an AI add-on the user installs next. Feature policies and extension policies are separate jobs.

Models land on the disk

On-device AI downloads model files. Usually harmless, but it is software on your fleet that nobody approved, and it uses disk and bandwidth.

Analysts say block for now

In December 2025 Gartner told security leaders to block AI browsers for now. Our summary of the Gartner advice covers what that means in practice.

Signs that AI is active in Brave or Firefox on your fleet

  • The Leo icon sits in Brave's sidebar or address bar
  • A separate AI browsing profile appears in Brave's profile list
  • brave://policy shows no Brave AI policies at all
  • The Firefox sidebar shows a chatbot provider's sign-in page
  • about:addons lists summariser, sidebar or agent add-ons
  • DNS logs show chatbot domains requested by Firefox or Brave

How to disable AI in Brave with group policy

Brave reads its own policies plus the Chromium policies you already know from Chrome. Two Brave policies cover the built-in AI. Extension policies cover the rest.

PolicySet toWhat it doesAvailable in
BraveAIChatEnabledfalse (DWORD 0)Turns off Leo, Brave's AI chat. Users cannot override a value you set.Brave builds on Chromium 121 and later
BraveLocalAIEnabledfalse (DWORD 0)Master switch for local AI: hides the features and stops on-device AI components from installing.Brave builds on Chromium 149 and later
ExtensionInstallBlocklistList of extension IDsBlocks the listed extensions. Installed copies are disabled and cannot be re-enabled.Chromium policy, supported by Brave
ExtensionInstallAllowlistList of extension IDsWith a blocklist value of *, only these extensions can be installed.Chromium policy, supported by Brave

Windows

Registry key HKLM\SOFTWARE\Policies\BraveSoftware\Brave, set by Group Policy with Brave's templates, by Intune, or directly in the registry.

Brave notes that Home editions of Windows do not support Group Policy, but the registry values still work.

macOS

Preference domain com.brave.Browser, delivered in a configuration profile from Jamf, Intune, Kandji or Mosyle.

Use a device-scope profile. Check the bundle ID casing your MDM expects in the current admin console.

Linux

A JSON file in /etc/brave/policies/managed/. The folder may not exist after install, so create it first.

Name the file anything ending in .json and keep one source of truth to avoid conflicts.

Windows: turn off Leo and local AI (run as administrator)

reg add "HKLM\SOFTWARE\Policies\BraveSoftware\Brave" /v BraveAIChatEnabled /t REG_DWORD /d 0 /f
reg add "HKLM\SOFTWARE\Policies\BraveSoftware\Brave" /v BraveLocalAIEnabled /t REG_DWORD /d 0 /f

Linux: /etc/brave/policies/managed/ai.json

{
  "BraveAIChatEnabled": false,
  "BraveLocalAIEnabled": false,
  "ExtensionInstallBlocklist": ["fcoeoabgfenejglbffodgkkbkcdhcgfn"]
}
  1. Deploy the policies to a small test group first: one Windows PC, one Mac and, if you have them, one Linux machine.
  2. Quit and restart Brave. These Brave policies do not refresh while the browser runs.
  3. Open brave://policy and check that each policy shows the value you set with status OK, not a conflict.
  4. Confirm the Leo icon is gone from the sidebar and that the agentic button no longer appears where Leo used to be.
  5. Roll out to everyone, then re-check brave://policy after each major Brave update.

Admins have reported Brave builds on macOS where Leo stayed visible although brave://policy showed it as disabled. Test on a real Mac before you rely on the policy, and keep the AI domains blocked on the network as a second layer.

Brave's AI browsing runs in its own profile with separate cookies and logins, which limits what an agent can reach. On company devices we still recommend switching Leo off by policy until you have decided to allow agents at all.

Block Claude in Chrome and other agent extensions in Brave

Searches like "claude for chrome in brave" show what users try next. Brave installs Chrome Web Store extensions, so a Chrome agent extension works there too. The fix is the same Chromium policy with Brave's path.

Claude (Chrome extension)

fcoeoabgfenejglbffodgkkbkcdhcgfn

Browser agent that can read pages and act in tabs

Manus AI Browser Operator

cecngibhkljoiafhjfmcgbmikfogdiko

General autonomous agent working in the browser

Nanobrowser

imbddededgmcgfhfpcjmijokokekbkal

Browser agent for web automation

Windows: add one ID per numbered value

reg add "HKLM\SOFTWARE\Policies\BraveSoftware\Brave\ExtensionInstallBlocklist" /v 1 /t REG_SZ /d fcoeoabgfenejglbffodgkkbkcdhcgfn /f
reg add "HKLM\SOFTWARE\Policies\BraveSoftware\Brave\ExtensionInstallBlocklist" /v 2 /t REG_SZ /d cecngibhkljoiafhjfmcgbmikfogdiko /f

Blocklist mode

List known agent extensions and leave everything else allowed. Easy to start, but it only stops what is on the list, so the list must be kept current.

Allowlist mode

Set the blocklist to * and allow only approved IDs. Stronger, but every new request goes through IT. See our guide to blocking AI browser extensions.

For the risks of the Claude agent itself, and how to block it in Chrome and Edge, read Claude in Chrome at work. The extension ID above is the one to use in Brave as well.

How to disable AI in Firefox with enterprise policies

Firefox has two AI policies. Which one you use depends on the Firefox version on your devices, and ESR fleets lag behind the release channel.

PolicyFirefoxFirefox ESRHow it works
AIControls149.0.2 and later153 and laterOne entry per feature with Value set to available or blocked, plus Locked. A Default entry covers every feature you do not name.
GenerativeAI144 and later140.4 and laterTrue or false keys: Enabled, Chatbot, LinkPreviews, TabGroups and Locked. Enabled set to false turns the features off by default.
AIChatbotCheck the current policy docs for supported editionsConfigures which chatbot providers appear in the sidebar. To switch the chatbot off, Mozilla points to AIControls.

policies.json for Firefox 149.0.2+ and ESR 153

{
  "policies": {
    "AIControls": {
      "Default": { "Value": "blocked", "Locked": true },
      "Translations": { "Value": "available", "Locked": false }
    }
  }
}

policies.json for ESR 140

{
  "policies": {
    "GenerativeAI": {
      "Enabled": false,
      "Chatbot": false,
      "LinkPreviews": false,
      "TabGroups": false,
      "Locked": true
    }
  }
}
AIControls keyCoversOur suggestion for company devices
SidebarChatbotThe AI chatbot panel in the sidebarBlocked, unless you offer an approved company chatbot
LinkPreviewKeyPointsAI summaries in link previewsBlocked
SmartTabGroupsAI tab grouping suggestionsBlocked or available: low data exposure, your call
SmartWindowSmart Window features (Firefox 150 and later)Blocked until reviewed
TranslationsAI page translation on the deviceOften allowed, because translation runs locally
PDFAltText, SpeechRecognitionOn-device alt text and speech recognitionAllowed where accessibility needs them

Windows

Group Policy or Intune with Mozilla's ADMX templates. Values live under Software\Policies\Mozilla\Firefox, for example AIControls\Default\Value set to blocked.

A policies.json file also works in a folder named distribution next to firefox.exe.

macOS

A configuration profile for the domain org.mozilla.firefox with EnterprisePoliciesEnabled set to true in the same profile. Install it with device scope.

Do not edit files inside the app bundle: that breaks the code signature.

Linux

System-wide file /etc/firefox/policies/policies.json, or the distribution folder of the install. Flatpak builds use their own path.

After any change, restart Firefox and open about:policies to confirm.

Block AI add-ons in Firefox by add-on ID

The AI policies switch off Firefox's own features. Add-ons need ExtensionSettings. Setting an add-on to blocked stops installation and removes it if it is already installed.

policies.json: block three AI add-ons

{
  "policies": {
    "ExtensionSettings": {
      "[email protected]": { "installation_mode": "blocked" },
      "{b13d04e3-41db-48b3-842c-8079df93c7ad}": { "installation_mode": "blocked" },
      "[email protected]": { "installation_mode": "blocked" }
    }
  }
}
  • WebBrain

    Browser agent add-on for web automation.

  • WebChatGPT

    Adds web results to chatbot prompts from the browser.

  • Dust

    Add-on for an agent platform that works across company tools.

  • Rules to remember

    UUID-style IDs keep their curly braces. On Windows the policy is stored as a JSON string, so most admins use the ADMX template or policies.json.

People also search for add-ons that hide AI summaries in search results. AI Overviews are part of Google Search pages, not a Firefox feature, so browser AI policies do not touch them. Treat those add-ons like any other: review before you allow.

How to disable AI in your browser: one map for every browser you allow

Most fleets run two or three browsers. Each one has its own switch, and AI browsers have no switch at all.

Chrome

Gemini in Chrome and its agent features have their own policies.

Disable Gemini in Chrome

Edge

Copilot Mode and the Copilot sidebar are managed with Edge policies.

Disable Copilot Mode in Edge

Brave

BraveAIChatEnabled = false

BraveLocalAIEnabled = false

Firefox

AIControls Default = blocked

ESR 140: GenerativeAI Enabled = false

AI browsers such as Dia or Comet are built around the assistant, so there is no policy that makes them AI-free. Block or remove them instead: see how to block the Dia browser.

What to block, what to monitor, what to allow

Browser policies are one layer. The table below is how we would set up a typical company that allows Brave or Firefox next to Chrome or Edge.

Block

  • Leo and AI browsing in Brave, by policy
  • The Firefox sidebar chatbot, link preview summaries and Smart Window
  • Agent extensions and add-ons by ID in both browsers
  • AI browser downloads and agent platforms by domain

Monitor

  • brave://policy and about:policies after every update
  • DNS requests to chatbot and agent domains
  • New extensions and add-ons in your device inventory
  • Other browsers appearing on devices

Allow

  • On-device translation where staff need it
  • Accessibility features such as PDF alt text
  • Approved AI tools on their own domains, under your AI policy
  • Approved extensions through an allowlist

Feature policies do not stop a user from opening a chatbot website. Pair them with domain blocking in your firewall or DNS filter so the same rules hold in every browser.

Keep Brave and Firefox in step with the rest of your fleet

Policies switch off built-in AI. Our list covers what users add on top: agent extensions, AI add-ons, AI browsers and agent platforms, updated every day.

Every entry has the tool name, category, identifier type and a risk grade, so you can block all agents or only the higher-risk ones. Read more about what the AI Agent Blocklist contains.

From $99 a month for one organisation

  • Chrome and Edge extension block lists, which also work in Brave's ExtensionInstallBlocklist
  • Firefox add-on IDs of agent and AI add-ons, ready for ExtensionSettings
  • 2,600+ AI agent domains as a plain list, hosts file, PAC file and firewall external list
  • macOS bundle IDs and Windows package IDs of AI browsers for Jamf and Intune
  • CSV and JSON with all columns, including the risk grade
  • Updated every day; download access set up within one business day of your order

Ask us or order a plan

Tell us what you need to block and where your rules live. We reply within one business day.

  • Files for firewalls, DNS filters, secure web gateways, MDM and browser policies
  • Updated every day as new AI browsers, agents and extensions appear
  • Plans for one organisation, for MSPs and for product makers, or a hosted filter we run for you

We use your details only to answer you. No newsletters.

Questions about AI in Brave and Firefox

How do I disable AI in the Brave browser for all staff?

Set the Brave policy BraveAIChatEnabled to false to turn off Leo, and on newer Brave releases set BraveLocalAIEnabled to false to hide local AI features.

Deploy them through Group Policy or the registry on Windows, a configuration profile on Macs, or a JSON file in /etc/brave/policies/managed on Linux. Then restart Brave and check brave://policy.

Can I block Claude for Chrome in Brave?

Yes. Brave installs extensions from the Chrome Web Store and supports Chromium policies, so add the extension ID fcoeoabgfenejglbffodgkkbkcdhcgfn to ExtensionInstallBlocklist under the Brave policy path. An installed copy is disabled and the user cannot switch it back on.

How do I disable AI in the Firefox browser?

On Firefox 149.0.2 and later, and on ESR 153, use the AIControls policy: set Default to blocked and Locked to true, then allow single features such as Translations if you want them.

On ESR 140, use the GenerativeAI policy with Enabled, Chatbot, LinkPreviews and TabGroups set to false and Locked set to true.

How do I block AI extensions in Firefox?

Use the ExtensionSettings policy and give each AI add-on ID the installation_mode blocked. Firefox then refuses to install it and removes it if it is already installed. UUID-style add-on IDs must keep their curly braces.

Is Brave's agentic AI browsing on by default?

No. Brave's AI browsing is opt-in and sits behind a flag. Since May 2026 it is available for early testing on all release channels. It runs in a separate profile. On managed devices, turn off Leo by policy and confirm on a test device that the agentic button is gone.

Is Brave a bad browser for company use?

No. Brave is a Chromium browser with documented group policies. The real question is whether it is managed. If you allow Brave, give it the same AI, extension and URL policies you give Chrome and Edge.

Does turning off AI in the browser stop AI websites?

No. Browser AI policies switch off built-in features. Chatbot websites, AI browsers and agent platforms are still reachable unless you also block their domains in your firewall, DNS filter or URL policy.

Brave and Leo are trademarks of the company that makes the Brave browser. Firefox is a trademark of the Mozilla Foundation. Chrome, Gemini and Google are trademarks of Google LLC. Microsoft Edge and Copilot are trademarks of Microsoft Corporation.

Claude is a trademark of Anthropic, PBC. ChatGPT is a trademark of OpenAI. Comet is a trademark of Perplexity AI, Inc. Dia is a trademark of The Browser Company of New York. Manus, Nanobrowser, WebBrain, WebChatGPT, Dust and other product names are trademarks of their owners.

Names are used only to identify the products discussed. AI Agent Blocklist is not affiliated with, sponsored or endorsed by these companies.