Feature: Allow user to select model (GPT, o1, o3, etc) per chat

[orngeatom]

Not an issue but a request to implement an azure chat model selector that can be selected at start of chat

[olafwrieden]

Nice idea! There are different capabilities in these models so for example some might do audio and image whereas others are purely text-based - some redesign / disabling features based on selected model may need to happen. You could put a model selector on the chat text box which is probably the best place as it's consistent between personas/extensions/chat pages and would require minimal changes to UI.

A challenge I see is deploying a multi-model approach with infra as code. This was the case with DallE which wasn't available in all Azure regions, meaning perhaps we take a GPT4o model as baseline for the IaC deployment, then allow deployments from AI Foundry to be configured via an array similar to how we handle configuration for Identity Providers. If a "custom" model deployment has been provided, the model selector becomes visible allowing the user to select the out of the box 4o or configured custom deployment.

Now we would just have to handle changes to the request body and function calling based on model schema and capabilities - maybe something Semantic Kernel could help with.

Example of Model Selector

[fsch-ppi]

I have a very simple implementation with a model slider that you can change when on a chat. I have extended the ChatThreadModel with the used model, the api call is then done to a respective endpoint depending on this attribute.

[fsch-ppi]

Short explanation for the dalle3 slider: Since the chatbot will quite often generate images even when not asked about it.
I have changed the code in a way, so that the ability to create images is only explicitly given to the chatbot, when the dalle3 slider is selected (gpt4o is the underlying model in our case).

As soon as MS unlocks us for the o3 model for an EU deployment we will also integrate that into slider and chat.