-
Notifications
You must be signed in to change notification settings - Fork 0
Description
🐛 Bug Description
When using a custom Ollama model in AutoSort+, the selected model continues to work correctly after restarting Thunderbird, but the Settings UI does not reliably reflect which model is actually in use. After reopening the settings, the custom model field may be blank or the model dropdown may show a default model (e.g. “Llama 2”) that is not installed, creating confusion about whether AutoSort+ has reverted to a default model or is still using the previously configured custom model.
📋 Steps to Reproduce
Open AutoSort+ Settings
Go to Local Ollama Configuration
Set Ollama Model to Custom (enter below)
Enter a valid installed model (e.g. qwen2.5:7b-instruct)
Click Save settings
Restart Thunderbird
Confirm AutoSort+ continues sorting emails successfully
Re-open AutoSort+ Settings
Observe that:
The custom model field is blank or
The model dropdown shows “Llama 2”, even though it is not installed
A warning may appear stating Model “llama2” not installed
❌ Expected Behavior
The Settings UI should clearly and accurately display the actual model currently in use
If a custom model is configured:
The custom model name should remain visible after restart
The model dropdown should not default to an uninstalled model
It should be immediately clear to the user whether:
A custom model is active
Or a fallback/default model is being used
👀 Actual Behavior
AutoSort+ continues to function and sort emails correctly
The Settings UI:
Clears the custom model field or
Displays a default model (e.g. “Llama 2”) that is not installed
This makes it unclear whether AutoSort+:
Is still using the custom model
Or has silently reverted to a default model
📸 Console Output
Browser Console Log (Ctrl+Shift+J in Thunderbird):
[No explicit Ollama errors observed during sorting]
[Warning shown in UI: Model "llama2" not installed]
🔧 Environment Details
Thunderbird
Version: [please fill in]
OS: Windows
OS Version: [e.g. Windows 11]
Ollama Setup
Ollama Version: [output of ollama --version]
Model Used: qwen2.5:7b-instruct
Running on: GPU (NVIDIA)
GPU Model: NVIDIA GPU with 12GB VRAM
Memory Available: 12GB VRAM
AutoSort+
Extension Version: autosortplus-1.2.3.3
Install Method: XPI
✅ Debugging Checklist
Ollama is running (curl http://localhost:11434/api/tags works)
Custom model installed and listed
Test connection passes
Sorting continues to work after restart
UI shows incorrect / misleading model state
Console shows clear indication of active model (not currently visible)
🎯 Additional Context
The issue occurs consistently
Appears limited to settings persistence and UI state
Functionality suggests the custom model remains active internally
The UI presentation makes it unclear which model is actually being used
📌 For Developers
This may be related to:
Model dropdown defaulting on settings reload
Custom model value not being rehydrated into the UI
Lack of a single “source of truth” for active model display
A possible UX improvement would be to:
Always display the active model name (including custom models)
Prevent fallback display of uninstalled default models

