Summary
After upgrading Factory Desktop from 0.80.1 to 0.81.0, previously configured custom BYOK models no longer appear in the desktop model selector UI.
The same custom model configuration still appears to be valid and usable by the daemon/CLI path: recent logs show requests using a custom model ID successfully, but the desktop UI does not list the custom models after the upgrade.
Environment
- Factory Desktop: 0.81.0
- Bundled
droid: 0.124.0
- Platform: macOS, arm64
- Previous working version: 0.80.1
- Custom provider type:
generic-chat-completion-api
Expected behavior
Custom models configured in user settings should continue to appear in the model selector after upgrading.
Actual behavior
The custom models disappear from the desktop model selector after upgrading to 0.81.0.
Notes from local diagnosis
~/.factory/settings.json still contains the custom model entries.
- The configured OpenAI-compatible
/v1/models endpoint is reachable and returns the configured model IDs when called with the configured API key.
- Recent Factory logs still show custom model usage with
modelId values like custom:<name> and modelProvider: generic-chat-completion-api.
- This looks like a UI/model-list regression or a stricter model-provider/schema validation change in 0.81.0.
Possible related area
The 0.81.0 desktop bundle appears to validate available model entries with a schema including fields like modelProvider, supportedReasoningEfforts, defaultReasoningEffort, and isCustom. Existing settings use custom model entries with a provider value of generic-chat-completion-api, so there may be a mapping/filtering mismatch when converting custom settings into availableModels.
Privacy note
I intentionally omitted the actual base URL, API key, and model display names because they include private infrastructure details.
Summary
After upgrading Factory Desktop from 0.80.1 to 0.81.0, previously configured custom BYOK models no longer appear in the desktop model selector UI.
The same custom model configuration still appears to be valid and usable by the daemon/CLI path: recent logs show requests using a custom model ID successfully, but the desktop UI does not list the custom models after the upgrade.
Environment
droid: 0.124.0generic-chat-completion-apiExpected behavior
Custom models configured in user settings should continue to appear in the model selector after upgrading.
Actual behavior
The custom models disappear from the desktop model selector after upgrading to 0.81.0.
Notes from local diagnosis
~/.factory/settings.jsonstill contains the custom model entries./v1/modelsendpoint is reachable and returns the configured model IDs when called with the configured API key.modelIdvalues likecustom:<name>andmodelProvider: generic-chat-completion-api.Possible related area
The 0.81.0 desktop bundle appears to validate available model entries with a schema including fields like
modelProvider,supportedReasoningEfforts,defaultReasoningEffort, andisCustom. Existing settings use custom model entries with aprovidervalue ofgeneric-chat-completion-api, so there may be a mapping/filtering mismatch when converting custom settings intoavailableModels.Privacy note
I intentionally omitted the actual base URL, API key, and model display names because they include private infrastructure details.