Mozilla put Mistral Small 4 inside Firefox Smart Window. The browser is now a distribution and policy surface for AI, so write the vendor file for it.

The AI story for Wednesday, September 16, 2026 is a browser partnership, and the part worth your attention is not the model. It is the door the model came through.

Mozilla and Mistral announced today, in matching posts on the Mozilla blog and Mistral's news page, that Mistral Small 4 is coming to the Firefox Smart Window beta. In the US and Canada, it shows up as a new model option alongside the models Smart Window already offered. In France, the announcement doubles as a launch: Smart Window beta becomes available there for the first time, with official French-language support. Mistral's post adds that the United Kingdom and Germany are expected to follow later this year. Mozilla's post says "additional European expansion later this year" without naming countries. Across every market where Smart Window beta is available, Mozilla says users can still choose from "a multitude of other AI models."

Both companies wrote the same sentence about privacy, and it is the sentence a small team should copy into its notes: conversations are not saved on Mozilla's servers by default, and partners like Mistral agree to zero data retention.

I want to walk through what was actually announced, why the framing from both CEOs is more than marketing, and why a five-person shop that has never thought about Firefox as a vendor now has one more line to write in the vendor file. Because the browser is where your team's tabs, history, and half-finished research live, and as of today it is also a place where a European frontier model can be selected from a menu.

What was announced, with dates attached

Last November. Mozilla showed an early concept called "AI Window," a user-controlled space for chatting with an assistant while browsing. This is from Mozilla's own August product post, which I read as background and not as today's news.

August 18, 2026. Mozilla published the Smart Window overview. Smart Window is described as Firefox's privacy-first, AI-powered browsing experience. It works with the context you choose to share, "such as your open tabs and relevant browsing history." That post added web retrieval through a partnership with Exa, tab grouping suggestions, and visual previews of pages in your history. It said Smart Window was available in English to people in the US and Canada, that users choose which AI model to use, and that Firefox's AI Controls give one place to manage it or turn it off entirely. It also previewed features that are not shipped yet: surfacing recent browsing journeys and helping fill out online forms.

September 16, 2026. Mozilla and Mistral announce the partnership. Mozilla names the model: Mistral Small 4, selected "after evaluating its performance for Smart Window Beta, including multilingual performance." Mistral's post describes Smart Window as "now powered by Mistral models" without naming the specific model, and says Mistral "will help power Smart Window for users in France and North America." Mozilla says the model is "coming to" Smart Window. Read those two verbs together and the honest summary is that the option is rolling out now, and you should check your own Firefox before assuming it is present. Mozilla also updated the August product post the same day to say Smart Window is rolling out in France, its first expansion beyond North America.

Note what was not announced. There is no enterprise product here. There is no admin console for a company to lock which model its employees see. Mistral's post is explicit that the company "traditionally focus[es] on serving the enterprise" and that this partnership is about reaching consumers. The controls described are per user, inside Firefox's AI Controls. That distinction matters for the checklist later.

Two CEOs described a distribution problem, not a model problem

Anthony Enzor-DeMeo, CEO of Mozilla Corporation, said the quiet part plainly: "We want to make sure that doesn't mean people are chained to one company's self-serving pipeline." And then: "A browser shouldn't be a one-way funnel."

Arthur Mensch, co-founder and CEO of Mistral, framed it as "two open source advocates working together," and Mistral's post listed four reasons the announcement matters, the first of which is "open technology needs open distribution."

Strip the idealism and this is a plain observation about where AI competition moved. Mozilla's own opening paragraph says the race has shifted from "which AI model is best?" to "which models people can access, through which products." A model that nobody can reach from the surface where they already work does not compete. A browser that ships one default assistant becomes, in Mozilla's word, a funnel. Mistral gets to reach Firefox users without owning a browser. Mozilla gets to integrate and recommend a model without removing choice. That is the deal, and it is a distribution deal.

Here is why this is not just a story about two companies you may not buy from. If the browser is now a place where models are distributed, then the browser is also a place where policy has to live. Every other surface where your team sends text to a model has a rule, or should. The IDE integration has a rule. The API gateway has a rule. The chat app under a company login has a rule. Firefox, until recently, was a way to open pages. Today it is a way to pick a model from a menu and hand it your tabs.

Read the privacy sentence the way a vendor reviewer would

"Conversations aren't saved on Mozilla's servers by default, and partners like Mistral agree to zero data retention." That is a good sentence. It is also a sentence with three edges a small team should notice.

"By default." A default is a setting. The August post says users choose what browsing context Smart Window can use and which model handles it. The privacy posture described today is the posture a fresh install has. It is not a guarantee about what a teammate's Firefox looks like after six months of clicking "allow."

"Partners like Mistral agree." That agreement runs between Mozilla and Mistral. You are not a party to it. If you are a Mistral enterprise customer you may have your own data processing terms, and that is a different relationship. If your designer uses Smart Window on a personal Firefox profile, the retention promise protecting her is a consumer promise from Mozilla, and the enforcement path is Mozilla's, not yours. That is fine for a personal browser. It is worth a sentence in your file when the browser is holding a customer's draft.

"A multitude of other AI models." The same menu that lets someone pick Mistral lets them pick anything else on it. Mozilla frames that as choice, and it is. From the operator's chair, it means the model your team's browser context reaches is decided by whichever teammate last opened the picker. The retention terms for those other models are theirs, not Mistral's.

None of this is a criticism of Mozilla or Mistral. They have built a more transparent posture than most default assistants and written it down in plain language. The point is that "privacy-first" is a product property and your vendor file is an operating document. They are related. They are not the same thing.

What "context you choose to share" actually contains

The August overview is specific about the raw material: open tabs, relevant browsing history, and, soon, recent browsing journeys and information to help fill out forms. Think about what those words mean on a working machine at a small firm.

Open tabs are your customer's staging site, the internal wiki, the pricing spreadsheet, the ticket you are triaging, and the half-written proposal in a docs editor. Browsing history is the list of every one of those over the past weeks. Form-fill data is names, addresses, and whatever else the browser has learned. A "research note" in Smart Window that leans on your open tabs is, functionally, a summary of the customer's project sent to a model, whichever model is selected.

This is the same egress question I wrote about on September 12 for agents reaching out to the internet, and on September 15 for engineers sending code to a second coding model. The direction is the same: your material, leaving your machine, toward a model. The new part is the container. Google let Claude in through Antigravity, a platform it controls, and kept the vendor's client barred. Smart Window is a consumer browser. The container is Firefox's own settings, controlled by the person at the keyboard.

Distinct from the last few notes

Yesterday was Google opening Claude Opus 5 to its engineers inside Antigravity on quotas. That is an internal policy at one company, through a container that company controls, and the model was a specialist for engineers. Today is a public consumer product, the container belongs to the end user, and the material at risk is tabs and research rather than code.

September 14 was three labs discussing a standards body. Multilateral, about the release bar. Today is bilateral and about distribution, which model reaches which users through which product.

September 8 was Mistral's Series D and the sovereign-AI pitch, read as a vendor-file update. Today is that pitch arriving on the consumer side, through a browser, with an actual retention promise attached. If you kept the four control questions from that note, the answers just got one more channel.

The small-team file: three sentences for the browser

If your team uses Firefox, or will, here is the smallest useful policy. It fits on a card. Write it before the first customer draft lands in the wrong assistant, not after.

1. Name the allowed models for Smart Window, or say none. "Mistral Small 4 only" is a policy. "Whatever the picker shows" is not. If you have already named a primary and a specialist path for your other tools, this list should be consistent with it, and it may well be "none" for work profiles. Firefox's AI Controls can turn Smart Window off entirely; that is a valid answer for machines that touch client data.
2. Name the browser context Smart Window may use. Tabs, history, or neither. The August post says the user chooses. Decide for work profiles, write it down, and check it. When browsing journeys and form-fill arrive, revisit this line, because those features expand what "context" means.
3. Write the logging and retention rule in your words. "Mozilla does not store conversations by default, Mistral has agreed to zero retention with Mozilla, and we do not turn on conversation saving on work profiles." Also write the honest caveat: the retention promise is between Mozilla and its partners, and other models on the menu have their own terms.
4. Separate work and personal profiles. A personal Firefox profile can do whatever its owner likes. The work profile is where the three sentences above apply. Firefox has supported profiles for years, and this is the cheapest control on the list.
5. Check the region before you assume the feature is there. Smart Window beta is in the US, Canada, and now France. UK and Germany are expected later this year according to Mistral. If you have a contractor in Berlin, their Firefox is different from yours today and may not be in December.
6. Put it on the review calendar. Smart Window is a beta that gained a model, a market, and a language in one day. The August post already previewed form-fill. Whatever you write now is a version 1, and the review date matters more than the wording.
7. Tell the team why, in one paragraph. People follow rules they understand. "The browser now has a model picker, and our tabs are the input" is a sentence a non-technical teammate can act on.

What not to do

Do not write "Firefox now uses Mistral." Firefox added a model option and kept the menu. Do not write "Mistral Small 4 is live everywhere." Mozilla says "coming to," Mistral says "now powered," the UK and Germany are later this year, and you should check the picker on your own install. Do not treat "zero data retention" as a term in your contract; it is a term in Mozilla's arrangement with its partners. Do not fold this into the Google-Claude story from yesterday; that was an internal policy through a company-controlled container, and this is a consumer browser with a menu. And do not skip the browser line in your vendor file because you think of the browser as neutral plumbing. As of today, in three countries, it has a model menu and read access to your tabs.

Bottom line

Mozilla and Mistral announced on September 16 that Mistral Small 4 is coming to the Firefox Smart Window beta, as a model option for US and Canadian users and as the launch model for France with official French-language support, with the UK and Germany expected later this year, other models still selectable, conversations not saved on Mozilla's servers by default, and zero data retention agreed by Mistral. Both CEOs framed it as a distribution deal meant to keep the browser from becoming one company's funnel, and they are right that this is where the competition moved. For a Fall River shop shipping client work, the actionable layer is that the browser is now a vendor path. Give it the three sentences every vendor path gets, allowed models, allowed context, logging rules, plus a work profile and a review date. If you want help writing that file for your own team, that is the kind of work we do.

Sources checked September 16, 2026: Mozilla blog, Mozilla and Mistral: Partnering to expand AI competition and preserve user choice (September 16, 2026); Mistral news, Mistral and Mozilla are bringing open, private and multilingual AI to your web browser (September 16, 2026); Mozilla blog, Smart Window: Finish what you start online (August 18, 2026, with a September 16, 2026 update noting the France rollout). The Smart Window overview is product background only; all partnership claims are drawn from the two September 16 posts.