- Issue created by @blainelang
- 🇺🇸United States kevinquillen
Yeah. At the time it was the simplest way to do model filtering, but they keep adding more and a regex will only get more complex. It was a way to keep people from selecting a model that wasn't going to work. Perhaps we should change that now.
- First commit to issue fork.
- @anjaliprasannan opened merge request.
- 🇮🇳India anjaliprasannan
The main changes are:
- For chat operations, now includes all GPT models including o3 models
- For JSON output capability, includes all GPT models without excluding mini versions
- For image vision capability, includes all GPT-4 models
- Removed unnecessary filtering of specific model versions
- Kept basic operation type filtering to ensure models are used for their intended purpose
-
marcus_johansson →
committed 66e2ae0c on 1.1.x
Issue #3514462: AiProvider plugin filtering out o3 models
-
marcus_johansson →
committed 66e2ae0c on 1.1.x
- Status changed to Fixed
3 months ago 6:44pm 22 May 2025 Automatically closed - issue fixed for 2 weeks with no activity.
- 🇨🇦Canada blainelang
I see the gpt-5 models now appear as options for the Chat operation but are filtered out for the Chat with Complex JSON which the AI Assistant / Chatbot and agents will use. Was there a reason for that?
// Include all GPT models for JSON output capability. if (in_array(AiModelCapability::ChatJsonOutput, $capabilities) && !preg_match('/^(gpt-4|gpt-4o|o1|o3|gpt-4-turbo)/i', $model['id'])) { continue; }
- 🇺🇸United States kevinquillen
Unavoidable at the time - open a new issue and should be an easy fix. In the long run we should probably figure out a better way to handle this, even though new numeric series models for OpenAI are not too frequent.