Description
Current implementation of model capabilities relies on the provider declaring the capabilities in one of the format that are supported (capabilities field and model name). However, the capabilities field is not a universal stamdard among providers. Covering all possible edge cases is complicated, therefore it would be good to have means to configure the capabilities per model in the config file and/or in the UI.
The models are already present in the config files in form of model field of agents (and fallback models), so this system of models written to config files would not change the state management of the LibreFang.
Alternatives Considered
Only possible alternative is to use AI gateway to wrap the provider. However, capabilities are not universally available even among AI gateway programs.
Additional Context
Closely connected with other issue: #4702.
Description
Current implementation of model capabilities relies on the provider declaring the capabilities in one of the format that are supported (
capabilitiesfield and model name). However, thecapabilitiesfield is not a universal stamdard among providers. Covering all possible edge cases is complicated, therefore it would be good to have means to configure the capabilities per model in the config file and/or in the UI.The models are already present in the config files in form of model field of agents (and fallback models), so this system of models written to config files would not change the state management of the LibreFang.
Alternatives Considered
Only possible alternative is to use AI gateway to wrap the provider. However,
capabilitiesare not universally available even among AI gateway programs.Additional Context
Closely connected with other issue: #4702.