Bugzilla

for actual implementation assuming we can rely on remote settings records https://searchfox.org/firefox-main/source/services/settings/dumps/main/ai-window-prompts.json

we would probably need to select the records for feature == chat (?) and the corresponding model_choice_id and potentially filter out for a relevant version, e.g., "2.*" if the current version of firefox does not know about / support "3.*" versions. i see there's an is_default field and various others that may be relevant to check

of course edge cases of what to do with multiple matches, e.g., version 2.10 vs 2.11, or somehow record missing for a given model choice id

unclear what should happen if we start applying the user model choice pref to non-chat prompts… e.g., potentially we say fast/1 = chat system prompt uses gemini while title generation prompt uses <fancy-other-model> (instead of the current remote record indicating to always use qwen)

for actual implementation assuming we can rely on remote settings records https://searchfox.org/firefox-main/source/services/settings/dumps/main/ai-window-prompts.json

we would probably need to select the records for feature == chat (?) and the corresponding model_choice_id and potentially filter out for a relevant version, e.g., "2.x" if the current version of firefox does not know about / support "3.x" versions. i see there's an is_default field and various others that may be relevant to check

of course edge cases of what to do with multiple matches, e.g., version 2.10 vs 2.11, or somehow record missing for a given model choice id

unclear what should happen if we start applying the user model choice pref to non-chat prompts… e.g., potentially we say fast/1 = chat system prompt uses gemini while title generation prompt uses <fancy-other-model> (instead of the current remote record indicating to always use qwen)