Dense 128B open-weight model merging chat, reasoning and coding, with per-request reasoning effort and 256K context.
Output Speed *
Intelligence Index *
Context Window *
Input price
Output price
Performance
Agentic Coding Results From a General-Purpose Dense Model
Benchmarks
Independent Measurements: Above-Median Intelligence, Good Throughput, Slow First Answer
Output Speed
Intelligence Index
MMLU *
GPQA *
HLE *
LiveCodeBench *
Technical Specifications
What the model supports
Limitations & Trade-offs
Best-Fit Workloads
Where this model earns its place
Coding agents
Mistral reports 77.6% on SWE-Bench Verified, and Medium 3.5 is the default model in Mistral's Vibe coding agent. That fits multi-file edits, repository-scale context within 256K tokens, and tool-driven fix loops. Use high reasoning effort for hard tasks. The score is vendor-reported, so run your own repository tests, and watch cost on long agent loops.
Tool-using research and workflow agents
The model supports native function calling in both modes and is reported at 94.2% on the τ²-Bench Telecom multi-turn tool-use benchmark. That makes it a candidate for agents that triage tickets, query systems and synthesize research. This is a narrow benchmark; broader agentic suites rank it lower, so test on your own tool schemas before trusting long autonomous runs.
Document and screenshot analysis
Medium 3.5 accepts text and image input through a vision encoder trained from scratch for variable image sizes and aspect ratios, and Azure lists PDF input. Artificial Analysis reports 69.3% on its AA-LCR long-context reasoning test. It suits invoice parsing, chart reading, UI screenshots and report extraction. Output is text only, so structured extraction should use JSON output.
Tiered chat and reasoning assistants
Because reasoning effort is a request parameter, one model can answer routine questions with reasoning off and escalate complex ones to high. This replaces maintaining separate chat and reasoning models, as Mistral did with Medium 3.1 and Magistral. The trade-off is that high effort increases latency and output tokens, so route by task difficulty.