Chat.extensionunification.enabled Jun 2026

Chat extensions have become an essential component of conversational AI, allowing developers to enhance the functionality of chatbots and provide a more engaging user experience. These extensions can range from simple integrations with external services to complex workflows that enable chatbots to perform tasks autonomously. However, with multiple extensions available, managing and integrating them can become a daunting task, leading to fragmentation and inconsistencies in the user experience.

The chat.extensionUnification.enabled setting controls a transition where all functionalities—completions, inline chat, and the chat panel—are migrated into the . Once unified, the original standalone Copilot extension is essentially deprecated or merged, reducing background overhead and simplifying updates. Why Enable Extension Unification? chat.extensionunification.enabled

This is where the concept of "Extension Unification" enters the picture. The flag chat.extensionunification.enabled was introduced during a transitional period where Firefox developers sought to decouple the browser from the responsibility of managing chat protocols. Instead of the browser asking the operating system how to handle an irc:// link, this feature allowed the browser to hand off that responsibility to installed extensions or the operating system’s default handlers. Chat extensions have become an essential component of

: Responsible for "ghost text" inline completions as you type. The chat

: Responsible for the interactive chat interface, slash commands, and complex agentic tasks.

chat.extensionunification.enabled=true