feat: add models settings page with filtering and management

[VirenMohindra]

Before Submitting This PR

Please confirm you have done the following:

• I have searched existing issues and pull requests (including closed ones) to ensure this isn't a duplicate
• I have read CONTRIBUTING.md

Description

adds a dedicated models settings page accessible from the sidebar, allowing users to view, download, switch, and delete transcription models without going through onboarding.

changes:

• add models settings page in sidebar with filter buttons (all/multi-language/translation)
• reuse ModelCard component from onboarding for consistent UI
• add model deletion with native confirmation dialog using tauri-plugin-dialog
• consolidate all model event listeners into useModels hook (removes duplicates from ModelSelector, LanguageSelector, TranslateToEnglish)
• gate AccessibilityPermissions component to macOS only (was rendering on all platforms)
• add is_recommended field to model registry for featured models
• remove unused get_recommended_first_model rust command (dead code)
• add translations for all 9 supported languages

Related Issues/Discussions

• related to model management improvements
• model registry discussion from [RFC] Handy UI Overhaul #449

Testing

• verified model download/switch/delete works from new settings page
• verified filter buttons correctly filter models by capability
• verified delete confirmation dialog appears (native macOS dialog)
• verified no duplicate event listeners (checked via code review)
• verified lint passes
• verified all translations present in 9 languages

Screenshots/Videos (if applicable)

n/a - UI reuses existing ModelCard component

state	demo
Model Section
Model dropdown
Dropdown downloading
Model Section "Extracting..."
Model auto switch after downloading
Delete confirmation

whisper	parakeet

[cjpais]

From first glance I'm digging this, I'd like to review around how model specific settings potentially overlap with this as well

[dannysmith]

Love this at first glance.

(Observation on looking screenshots: It might look nicer if the download/delete buttons on the ModelCards were to the left of the accuracy/speed bars. The bars are always present so should be consistently positioned?)

[VirenMohindra]

I'd like to review around how model specific settings potentially overlap with this as well

can you expand on that a bit? is there anything on the roadmap that could build on this? my goal was to put a solid foundation in place for future models -- things like tagging, filtering for now, and eventually search once the list grows

if there’s something that makes sense to support now while i’m already working in this area, happy to add it

It might look nicer if the download/delete buttons on the ModelCards were to the left of the accuracy/speed bars

yeah, i experimented with that briefly, and i think you’re pointing out that downloading a model causes the accuracy / speed bars to shift, which isn’t ideal

at the same time, i was trying to keep things consistent between the model dropdown and the model selection tab, and we generally place destructive actions on the far right

open to alternative layouts if you have something specific in mind

[cjpais]

@VirenMohindra regarding

can you expand on that a bit? is there anything on the roadmap that could build on this?

Yeah definitely. Right now there's a bit of awkwardness in that whisper supports translation built in as well as language selection. But parakeet the language is always "auto" and there's no translation built in. So it's just trying to disambiguate this in the UI since I think it could be confusing for some users. I think we just disable those settings for parakeet, which is okay but it's not super obvious why they are disabled

I was considering making them invisible to the UI for parakeet, but just curious about feedback or other potential UX ideas around this

[VirenMohindra]

@cjpais that makes sense. current state: settings are disabled with explanatory text, but that can feel clunky

i went ahead and implemented a contextual approach in this PR — there's now a "model settings" card in general settings that adapts based on the current model:

• whisper models show language selector + translation toggle (when supported)
• parakeet models show "this model works automatically with no configuration needed"

this way users only see settings that apply to their model, no more confusing disabled / grayed out options. let me know if you'd prefer a different approach or want any adjustments

whisper	parakeet

[cjpais]

Wow this is much nicer. Thank you @VirenMohindra

I don't think I'll be able to review this for a bit but I think we should try and have this be part of a v0.7.0 release

I don't know how reasonable it would be, but it would be very cool to have some filtering on language or something like that in the model page too. So you could pick your specific language and make sure the model you're using supports that language. Mainly I know some people have had problems in the past creating issues for example that Parakeet doesn't support their language well

[VirenMohindra]

Wow this is much nicer. Thank you @VirenMohindra

❤️❤️

I don't think I'll be able to review this for a bit but I think we should try and have this be part of a v0.7.0 release

no worries. def would love a couple more eyes on this since it's a thicc one

I don't know how reasonable it would be, but it would be very cool to have some filtering on language or something like that in the model page too. So you could pick your specific language and make sure the model you're using supports that language. Mainly I know some people have had problems in the past creating issues for example that Parakeet doesn't support their language well

Great idea -- I actually played around with this but didn't want to blow out scope since we're already crossed a thousand lines of code. happy to take a peek and add it back in, or have a quick follow up PR

what do you think?

[cjpais]

Since it's already large, I'm happy to just do a full review of the feature as a whole here I think. I pretty much know I'm going to have to sit down with it already so a couple hundred lines more of code will probably be best now rather than later. I'll probably have some more detailed feedback at some point as well

[VirenMohindra]

done! added the ability to filter by language. opted to keep it on the frontend since we already had access to LANGUAGES. still relies on the BE via supports_language_selection flag

all languages	simplified chinese filtered

cc @cjpais for vis

[cjpais]

Thank you for the continued work on this. I'm quite excited to bring this in. I really need to play with it myself. It's been a long time and I don't want to let this get too stale. I'm really busy, but maybe within the next week or two I can make some more concrete decisions. It is quite a a big change, so it probably will take a bit longer for me to ensure this, but I'm liking generally where it's at and I can probably make some tweaks myself to clean anything else up.

[VirenMohindra]

@cjpais thanks for the update! no rush at all - take the time you need to review thoroughly. the feature is working well and we've addressed the cancel functionality issues mentioned here. happy to make any adjustments based on your feedback when you get a chance to test it out

[cjpais]

I just want to say a huge shout out for all this work! Thank you for bearing with me and getting this merged, but I think it's good to go. Super excited to get this in. I think this improves a bunch of UI and leaves a lot more room for future improvements as well. Thank you!