Back to rankings

Mistral Vibe: Smarter File Reads and Head-and-Tail Tool Output

Mistral VibeView original changelog

Mistral Vibe 3.0.1 improved how the agent reads files and handles long output. Tool output past about 16,000 characters is saved to a file, and the model sees its start and end. read_file now lists directories, reports line counts, and returns up to 64,000 bytes per call.

Key Takeaways

  • Long tool output is saved to a file, and the model sees both the start and the end.
  • Seeing the tail matters because errors usually appear at the end of logs and test runs.
  • read_file on a directory now lists up to 500 entries instead of failing.
  • read_file reports line counts and where to continue, which guides paging through large files.
  • The per-call limit rose from 51,200 to 64,000 bytes, in line with the Agents SDK.
  • An offset past the end of a file is now a clear error rather than an ambiguous result.

Better context from file reads and long output

Mistral Vibe 3.0.1 changed how large tool results and file reads reach the model, so the agent gets more useful context with fewer wasted calls.

Long tool output keeps its start and end

When a tool produces more than about 16,000 characters, Vibe saves the full output to a file. The model now sees both the beginning and the end of the output rather than only the beginning. This matters for logs and test runs, where the failure message is usually at the bottom.

read_file improvements

read_file now reports the file's line count and where to read on, and an offset past the end of the file is an explicit error. Calling read_file on a directory lists its entries, up to 500 at a time, instead of failing. Both read_file and file mentions now return up to 64,000 bytes per call, up from 51,200, matching the Agents SDK.