PARAS MADAN
All writing

Latest in AI

Firefox Smart Window Adds AI Form Filling and Page Watching

Firefox can use selected tabs to fill forms and watch pages for changes, but its new tasks are not always-on cloud agents.

Mozilla announced two additions to Firefox Smart Window on October 27: form filling from selected browser tabs and scheduled webpage monitoring. They move its AI assistant beyond answering questions, while keeping important limits around what it can submit and when it can run.

Mozilla's announcement describes an opt-in beta for desktop users in English in the US and Canada. This is not a global release of autonomous browsing.

How Firefox AI form filling works

Open a supported form in Smart Window and select Fill from sources from an input field. Firefox suggests relevant open tabs, but you choose which ones it can use. It generates proposed entries for review before filling the form. You still submit it yourself.

That is different from saving an address for ordinary autofill. A selected profile page could supply the details for a registration form without requiring you to copy each answer separately. The useful boundary is the source selection: a browser with many open tabs should not treat every tab as relevant evidence.

Mozilla's form-fill documentation says this feature uses Gemini 3.1 Flash Lite, regardless of the model selected for assistant chat. Existing locally saved autofill information, such as addresses and payment details, continues to be filled from the device without being sent to an AI model.

The AI-assisted path is separate. Mozilla says information from the selected source pages is shared with the model to produce suggestions. Local autofill does not mean local AI inference. Review both the chosen tabs and the resulting values, especially when a form contains information you would not otherwise send to a model provider.

How page-watching tasks work

You can type /watch in Smart Window chat, describe the change you want to detect and add the relevant pages. Mozilla supports daily or weekly checks. The browser must be open for checks to run.

The task documentation allows up to five webpages per task and 15 active tasks. Tasks use Qwen rather than your selected chat model. Matches appear in the Tasks interface and can trigger desktop notifications.

The task documentation says tasks automatically pause after 60 days without a match, and all tasks pause 90 days after creation. They can be reviewed and resumed. On macOS, Firefox notifications need to be enabled separately in system settings.

For someone watching a product page or checking when a registration opens, this could replace a small recurring browsing chore. It should not be treated as a guaranteed alerting system for a time-sensitive business process. A laptop that is shut down cannot perform its scheduled browser check.

The limits matter more than the demo

The form-filling release currently handles text fields. Mozilla describes broader field types and PDF support as areas it is exploring, not functionality available in this announcement. AI suggestions can also be wrong even when the source page contains the right answer.

Firefox 159's release notes mark page watching as a progressive rollout, so an eligible installation may not receive it immediately.

The practical test is whether the review costs less attention than doing the work manually. Checking five suggested entries can be useful; correcting confidently misplaced information is less useful. Browser automation becomes easier to trust when its source material, proposed action and execution limits are visible at the point where someone needs to decide.

I’m Paras. I work at the intersection of AI, engineering and distribution.

I help technical founders turn product capabilities and their real limits into launch stories that developers can understand and share.

Book a 30-minute call.