What changed
Mistral’s November 5 announcement expands Studio with managed agents and apps, plus updates to workflows, shared business context, and tools for inspecting and evaluating runs. The update is about how teams put models to work. Mistral Large 4, also called Le Chonk, was already available. [1]
An agent can use approved tools to investigate a problem. A workflow can put fixed steps, agent decisions, and human approvals in a defined order. Mistral says the update adds event triggers and a visual graph for workflows. Studio apps give employees an interface for using those systems. [1] [2] [3] [4]
Check where each part runs
In Mistral's hybrid setup, the workflow code runs on your own machines. Studio still manages the state, history, and delivery of tasks to those machines. Check where the model runs and where inputs, outputs, and run records are stored. Confirm the options for your own deployment. [2] [3]
Our take
Try one fictional support request and a simulated ticket system. Have the workflow suggest a team, then ask a person before creating the ticket. Interrupt a test run after the simulated system accepts the ticket, then resume it. Check whether the run recognizes the first ticket or creates a duplicate. A visual graph helps you see the steps. The restart test shows what the steps actually do.
This briefing is based on Mistral's announcement and documentation.