Back to rankings

Mistral Vibe: Bash Tool Now Loads Your Login Profile and Uses Shorter Timeouts

Mistral VibeView original changelog

Mistral Vibe 3.0.1 reworked how its bash tool starts shells. The login profile now runs before a session's first command, so commands can call functions and aliases it defines in bash and zsh. A timed-out command now returns the output it had printed, and the default timeout is 120 seconds (up to 300 on request).

Key Takeaways

  • The login profile now runs before the first command, so the agent sees the same environment as the user's shell.
  • Commands can call profile-defined functions and aliases in bash and zsh.
  • A timed-out command returns its partial output, which makes hangs easier to debug.
  • The default bash timeout is now 120 seconds, up to 300 when asked.
  • A slow or failing profile is skipped after 10 seconds with a warning instead of stalling the session.
  • An inverted default_timeout and max_timeout_seconds pair is now a clear config error instead of a silent clamp.

Shell behavior that matches the user's terminal

Mistral Vibe 3.0.1 changed several defaults in the bash tool so that agent commands behave more like commands typed in the user's own terminal.

Login profile support

The shell's login profile now runs before a session's first command, and outside that command's timeout. A profile that fails, or that takes longer than 10 seconds, is skipped with a warning instead of blocking the session. For bash and zsh, commands can now call the functions and aliases the profile defines, and a change to a profile file is picked up by the next command. Vibe also fixed cases where commands lost PATH entries that a login profile resets, and the profile now runs once per session.

Timeouts

A bash command that times out now returns whatever it printed before the deadline, which helps the agent diagnose a hang instead of seeing only a failure. The default timeout is now 120 seconds, extendable to 300 seconds when requested. The tools.bash.default_timeout and max_timeout_seconds settings stay unset unless set in config.toml, while the native shell tools still default to 300 seconds with a maximum of 600 (or the default, if that is longer). A shell tool whose default_timeout exceeds its max_timeout_seconds is now a config error naming both values, rather than being silently lowered.

Smaller fixes

Bash commands also keep working after a command deletes /dev/null.