I maintain WebBrain, an open-source (MIT) AI browser agent for Firefox. It reads pages, extracts data, and automates browser tasks using a model of the user’s choice, and it can run fully local via llama.cpp or Ollama, so it works entirely offline with nothing leaving the user’s machine. It’s listed on AMO and developed in the open on GitHub.
I submitted a nomination through the official amo-featured address recently, and I understand Recommended is tightly curated with limited slots, so I’m not chasing a decision or expecting one quickly. What I’d like to understand better is the process itself:
Roughly what timeline is normal between nomination and any kind of response? Is silence the usual outcome when something isn’t selected?
Is there anything useful a solo developer can do to prepare — documentation, clear permission rationales, review readiness — or is the nomination simply evaluated as-is?
For a permission-heavy extension (this one uses the debugger API for reliable input in its act mode), is there anything reviewers particularly want to see documented up front?
Happy to be pointed at existing docs if I’ve missed something obvious. Mostly I’d rather do the preparation properly than keep wondering whether I’ve left something undone.
Hi there. I’ll try addressing some of your questions… Timelines for candidate consideration can vary considerably because we typically process nominations through temporary community curatorial projects (usually spanning a number of months), but these projects do not run all the time, because they’re supported by volunteer contributors who offer their time for careful analysis of large pools of content. So the practical reality is there can be significant gaps in time between curatorial projects.
Historically we’ve had limits on the number of Recommended Extensions the program can support because from a resource standpoint we can only realistically monitor a certain threshold of Recommended Extensions. However we are actively improving our review tools and monitoring capabilities and we’re aiming to soon expand the Recommended program to accommodate more curated content.
We just recently concluded a curatorial project and it’s yet undetermined when the next will run, but I see WebBrain in the nomination queue so it will be considered.
As for helpful documentation or tips, everything you need to know is detailed on Extension Workshop.
Thank you for building what looks to be very interesting content for Firefox users. Best of luck with WebBrain!
Thanks for the update and the encouragement! I appreciate the insight into how the Recommended program works and I’m happy to hear WebBrain is in the nomination queue.
I will keep you updated with any significant developments on my end.