Back to rankings

Mistral Vibe: Custom Python Tools No Longer Load, Migrate Them to Skills

Mistral VibeView original changelog

Mistral Vibe 3.0.4 stopped loading custom Python tools from ~/.vibe/tools/ and .vibe/tools/. Each such file now triggers a startup warning, and users are told to ask Vibe to migrate it to a skill. The release also removes the tool_paths setting from config.toml at startup, leaving the listed folders on disk.

Key Takeaways

  • Mistral Vibe 3.0.4 no longer loads custom Python tools from ~/.vibe/tools/ or .vibe/tools/.
  • Each affected file now produces a startup warning, so the change is not silent.
  • The recommended path is to ask Vibe to migrate the tool to a skill.
  • The tool_paths setting is removed from config.toml at startup, though the folders it listed remain on disk.
  • Settings under a built-in tool's name are now checked even if a custom tool of that name used them.
  • This is a breaking change for anyone relying on Python tool files, so upgrading users should review warnings on first launch.

A Breaking Change for Custom Tools

Mistral Vibe 3.0.4 no longer loads custom Python tools from ~/.vibe/tools/ or from a project's .vibe/tools/ folder. Anyone who extended Vibe by dropping a Python file into one of those locations will find that the tool silently stops being available. To avoid confusion, Vibe shows a warning at startup for each such file, and suggests asking Vibe itself to migrate the tool to a skill.

The tool_paths Setting Is Removed

Alongside this, the tool_paths setting no longer does anything. Vibe removes it from config.toml at startup. The folders it listed stay on disk, so no user files are deleted, but they are no longer scanned for tools.

Related Settings Checks

Settings placed under a built-in tool's name, such as [tools.web_fetch] proxy_host, are now validated even when a custom tool of that name used to consume them. This closes a case where a custom tool could shadow a built-in tool's configuration.

What Users Should Do

Users with custom tools should read the startup warnings, then ask Vibe to convert each tool into a skill. Skills continue to be supported and are picked up from disk, so the migration path keeps the same functionality in a supported form.