AI Council

Thanks for flagging this - you are right, and the bug is on us. Mistral’s /v1/models endpoint reports its models with a type value our filter was not expecting, so the listing was being silently dropped to zero. Every Mistral chat model your key can access (mistral-large, medium, small, codestral, ministral, devstral, magistral, pixtral, open-mistral-nemo) was unreachable because of it. The fix is in the next release, now in review. Once it lands, deleting and re-entering your Mistral key, or hitting “Test” again, will pull the full catalogue. The same release also fixes the custom OpenAI-compatible provider issue and the “network connection was lost” pop-ups on follow-up replies. Sorry for the frustration caused.

Thank you for updating your review - it genuinely means a lot to us. AI Council coordinates multiple providers, concurrent API calls, anonymised peer review across models, and file and image handling. Ensuring reliability across all combinations of models and settings is complex, and issues do occur as you found out. Your original feedback identified key gaps and directly influenced what was prioritised. Good to see the custom groups working - the speed versus deep-thinking split is a core use case. Thank you for your patience and please do feedback with any features you feel may be worthwhile adding (or indeed if you spot any more gremlins!).