I've been using it since February this year almost exclusively. Occasionally ran the same prompt through openrouter to check if it's "my context" or "the model" when I get a poor result.
Mistrals models aren't the best. They certainly are measurably worse when I run them "blank slate". That is: without skills, AGENTS.md, MCPs and so on. But who does that anyway?
Aside from these harnesses, I run many one-off agent threads. They run at most half an hour and fill the context window not even 20% before I stop and "handover". And I tend to be annoyingly demanding and nitpicky in my skills, AGENT.md, prompts and issues (that an agent uses as prompt).
In my workflow, the context is what makes or breaks how well the task is performed almost all of the times. Mistrals models aren't "the best" - some Chinese models are cheaper (with similar outcome), and anthropics' models outperform the output consistently but for 20x or more of the price of Mistral (that is: when using the API/token pricing). But Mistrals models are certainly "good enough". Good enough is good, too.
Mistrals models aren't the best. They certainly are measurably worse when I run them "blank slate". That is: without skills, AGENTS.md, MCPs and so on. But who does that anyway?
Aside from these harnesses, I run many one-off agent threads. They run at most half an hour and fill the context window not even 20% before I stop and "handover". And I tend to be annoyingly demanding and nitpicky in my skills, AGENT.md, prompts and issues (that an agent uses as prompt).
In my workflow, the context is what makes or breaks how well the task is performed almost all of the times. Mistrals models aren't "the best" - some Chinese models are cheaper (with similar outcome), and anthropics' models outperform the output consistently but for 20x or more of the price of Mistral (that is: when using the API/token pricing). But Mistrals models are certainly "good enough". Good enough is good, too.