AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs That's awesome, but honestly that feature should have landed months ago. It's sad that it took so long to deliver such a 'simple' feature — it eroded trust needlessly

I understand it's hard to ship stuff, but we are talking about a toggle in preferences, so it was really frustrating not to see this shipped earlier.
Also, is that 'scare screen' really necessary? It's the same kind of trick we're always complaining about with FAANG products…
-
I know you'll likely get a whole bunch of negative feedback on Fedi for not going even further, but at least this appears to *clearly and unambiguously* put the user in control in a way that does not require digging through about:config settings and worrying about what an upgrade will do. So I am cautiously optimistic about this.
Can you say anything about when those of us who are on the ESR update track can expect to see this? Will there be a policy setting to control this?
@mkj @firefoxwebdevs policy example:
{
"policies": {
"DisableFirefoxStudies": true,
"DisableTelemetry": true,
"DontCheckDefaultBrowser": true,
"FirefoxHome": {
"SponsoredStories": false,
"SponsoredTopSites": false,
"Stories": false
},
"GenerativeAI": {
"Enabled": false
},
"SearchEngines": {
"Remove": [
"Perplexity"
]
}
}
} -
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs love it! Its a refreshing alternative to Edge's "shove Copilot down users thought at every opportunity" switch, which I think has only one setting
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs that being said, I actually love having local translation built into thr browser. It seems like the perfect use case for small language models that can be run on most laptops / desktop pcs today. Don't see a need to have the default setting to be off for that
-
@firefoxwebdevs
You are missing the point!The features should not exist! So then no need for a master switch in the main settings.
Firefox has got so broken it needs loads of settings changed in About.config and even then is LESS USEABLE than 10 or 15 years ago.
I've been using Websites since 1994. Mosaic, Netscape, Firefox.
Of course I've used most of the others.
@raymaccarthy @firefoxwebdevs You have never needed to use about:config. You can still quite happily browse the web using Firefox without going into about:config.
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs what's about mozconfig.cfg build option?
-
some people really like those other features though. Translation is one of our most requested features ever, and we couldn't implement prior to local AI. We weren't going to ship your web pages to some web service so they could see what you browse. But to other folks "AI is AI" and they want it off.
Feedback in Nightly is how we figure out if there are too many options or not enough.
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs the tiny minority of people who choose to use firefox at all dont want AI. it should be off by default if its being shoehorned in anyway, but since mozilla doesnt care the least they could do is not neuter the name.
"kill switch" bites, "AI controls" licks
EDIT: misread formally as formerly, still dont like this
-
@mkj @firefoxwebdevs policy example:
{
"policies": {
"DisableFirefoxStudies": true,
"DisableTelemetry": true,
"DontCheckDefaultBrowser": true,
"FirefoxHome": {
"SponsoredStories": false,
"SponsoredTopSites": false,
"Stories": false
},
"GenerativeAI": {
"Enabled": false
},
"SearchEngines": {
"Remove": [
"Perplexity"
]
}
}
} -
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs Do you know if there will be a popup to let users know when it launches? (Like a product tour "what's new" type of thing?)
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
@firefoxwebdevs boooo. AI shouldnt even be in the browser. Thats what the people told you.
-
@firefoxwebdevs please, set the block as active by default and only set AI features as "opt-in"
@madduci @firefoxwebdevs afaik the default is already opt in in a way - for example, the link summary feature asks you if you want to enable summarisation before actually doing anything.
the point of the block is a browser wide, 'don't even ask' toggle
-
@raymaccarthy @firefoxwebdevs You have never needed to use about:config. You can still quite happily browse the web using Firefox without going into about:config.
@plwt @firefoxwebdevs
The word "happily" is out of context.I have used Chrome (Android/ChromeOS)_, Edge (windows), IE (various cursed versions on Windows) and Safari (Apple Things) to "browse the web" and get a different browser such as Firefox, seamonkey, Vivaldi, Waterfox, Chromium and others.
I'd be on Vivaldi if about:config didn't exist. The only reason I'm not is more flexible script blocking on Firefox to suit TheGuardian web news.
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
NOBODY ASKED FOR THIS AI BULLSHIT!!!you’re traitors to the open web cause. this should have been an extension, not a complete integration in the browser.
-
@ArneBab but it doesn't enable future feature by default.
You're blocking the entry points to these features, so they cannot be enabled.
-
@plwt @firefoxwebdevs
The word "happily" is out of context.I have used Chrome (Android/ChromeOS)_, Edge (windows), IE (various cursed versions on Windows) and Safari (Apple Things) to "browse the web" and get a different browser such as Firefox, seamonkey, Vivaldi, Waterfox, Chromium and others.
I'd be on Vivaldi if about:config didn't exist. The only reason I'm not is more flexible script blocking on Firefox to suit TheGuardian web news.
@raymaccarthy @firefoxwebdevs Keen to understand more - why do you need to block scripts to be able to view the Guardian website?
What happens when you try to view the page without this?
Is there any error message?
-
@plwt @firefoxwebdevs
The word "happily" is out of context.I have used Chrome (Android/ChromeOS)_, Edge (windows), IE (various cursed versions on Windows) and Safari (Apple Things) to "browse the web" and get a different browser such as Firefox, seamonkey, Vivaldi, Waterfox, Chromium and others.
I'd be on Vivaldi if about:config didn't exist. The only reason I'm not is more flexible script blocking on Firefox to suit TheGuardian web news.
@raymaccarthy @plwt fwiw Vivaldi does have AI features like translation, and it even sends text to the cloud to perform that translation.
-
AI Controls (formerly 'kill switch') are landing in today's Firefox Nightly, and will land with Firefox 148 later this month.
For the full details, see the Firefox blog https://blog.mozilla.org/en/firefox/ai-controls/
Immediately restore the work of japanese language translators that you paved over with AI slop
AI Controversy Forces End of Mozilla’s Japanese SUMO Community
The SUMO Japanese team quits en masse, accusing Mozilla’s AI system of erasing years of community translation work.
Linuxiac (linuxiac.com)
-
@madduci @firefoxwebdevs afaik the default is already opt in in a way - for example, the link summary feature asks you if you want to enable summarisation before actually doing anything.
the point of the block is a browser wide, 'don't even ask' toggle
-
@firefoxwebdevs Do you know if there will be a popup to let users know when it launches? (Like a product tour "what's new" type of thing?)
@mausmalone I don't think so. But of course it will be mentioned in release notes. We're not exactly being quiet about it.