Introducing Mistral Code
Mistral AI
Mistral just launched a coding assistant built for big companies, not solo devs. It bundles its own models, security controls, and support so IT teams stop blocking AI copilots at the pilot stage.
Based on reporting by Mistral AI — read the original for the full story.
Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error
Mistral AI wants to solve a problem that's been quietly stalling AI coding tools inside big companies: nobody trusts the black box enough to let it near proprietary code. Mistral Code, launched today in private beta for JetBrains and VSCode users, is the company's answer — a coding assistant where the models, the plugin, and the enterprise controls all come from a single vendor, under a single SLA, with every line of code staying inside the customer's own infrastructure.
The product runs on four Mistral models working in tandem: Codestral handles autocomplete, Codestral Embed does code search, Devstral tackles agentic multi-step tasks, and Mistral Medium powers the chat interface. That's a deliberate split from the usual copilot setup, where a company might license a plugin from one vendor, a model from another, and host infrastructure with a third — a arrangement that Mistral says routinely dies in the details once CISOs and platform leads start asking hard questions. Mistral spoke with VPs of engineering and security chiefs and found the same four complaints kept surfacing: copilots that can't touch internal repos, models nobody can customize, tools that stop at suggesting code rather than finishing tickets, and support spread thin across vendors who all point fingers at each other.
What's notable is how far Mistral is pushing the
My take — AI-written commentary, not fact-checked reporting
I like that Mistral is fixing the actual thing enterprises complain about — SLA sprawl and no fine-tuning rights — rather than just shipping another chat window bolted onto an IDE. Deploying air-gapped for a bank and serverless for a railway in the same release shows real flexibility, not marketing flexibility. My only worry: forking Continue and promising upstream contributions 'in forthcoming releases' is the kind of open-source goodwill pledge that's easy to make and easy to quietly forget.
Read more about this at: Mistral AI