Have you confirmed that it’s working for other settings set in your .cfg file?
If so, and if it’s just the browser.ai.control settings that aren’t working, the first thing I would try is using lockPref[1] instead of just pref[2] and see if that fixes the issue.
If that doesn’t work, my next guess is that because it’s a just released feature (that almost certainly had it’s release date pushed up to address popular demand), they may not have implemented these settings as config/policy based settings yet. I’m not sure if I’m correctly interpreting this open bugzilla issue, but it sounds like that may be what it’s referring to. You may need to wait until a future release, to manage these settings via cfg.
lockPref(prefName, value) – sets the default value of a preference and locks it. This is the most commonly used function. Locking a preference prevents a user from changing it, and in most cases, disables the UI in preferences so it is obvious to the user that the preference has been disabled**. ↩︎
pref(prefName, value)– sets the user value of a preference. This function explicitly sets the preference as a user preference. That means that if the user has changed the value, it will get reset every time the browser is started. ↩︎
– Open the configuration file and save it (Ctrl+S) anywhere on your computer. Make sure the file is called “policies.json” (without the quotes).
– Open a new Terminal window in the directory where the file is located. For example, if it’s in your Downloads folder, open a Terminal and run cd ~/Downloads to switch to the Downloads directory.
– Create the Firefox policies directory with this command: sudo mkdir -p /etc/firefox/policies/
– Copy the file to the new folder: sudo cp ./policies.json /etc/firefox/policies/
– Restart Firefox.
To remove the custom configuration, delete the policies.json file from the distribution folder and restart Firefox. You can do that in the Terminal: sudo rm /etc/firefox/policies/policies.json
Or just /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/corbindavenport/just-the-browser/main/main.sh)"
i can but i think it’s better to disable AI at system level because a update in the future could re-enable them if you put a user.js in home directory (this is what i ithink). we don’t know yet what AI in browser is capable of
i tried to add those values it doesn’t work as soon i put the value firefox ignore my firefox.cfg and start without my pref i also tried to use “user_pref” in the firefox.cfg but that doesn’t work either
i tested lockPref it doesn’t work either look like it’s impossible now to disable AI by using firefox.cfg
yes i deleted the AI value and my firefox.cfg was working as excepted but when you add the AI value it doesn’t work anymore
well look like i have to switch to a another browser until they allow us to remove AI in firefox.cfg
Place this file in the root directory of the Firefox profile you want it applied to. You can learn about your Firefox profiles by accessing about:profiles in the address bar.
Okay, thank you for the correction. I am using Firefox ESR, so I do not have to think about any of these preferences until the ESR 153 branch on July 21st.
Maybe (or maybe not). What is it that you are trying to disable?
Afaik, it’s been possible to disable any of the AI features since they were introduced. The AI “killswitch” as I understand it is just a more convenient way for people to easily control AI settings from the GUI all in once place, and/or all with one single master toggle.
But if you are already using one of Firefox’s advanced configuration methods, it has already long been possible to disable the current AI features. I think the settings below will handle all of the existing features that the new AI GUI settings panel covers:
settings to disable AI chat in sidebar & context menus
settings to disable auto-generated alt text for images
pdfjs.enableAltText
settings to disable the API that allows extensions to use the browser for AI features
extensions.ml.enabled
I’m not sure what this setting currently does, possibly a placeholder for future use?
browser.ml.enable
Just to be clear, I don’t personally think that force-disabling these features improves privacy, just trying to provide helpful info for your goal of eliminating all AI features.