Mistral Vibe: /goal Keeps Working Across Turns Until Done

Mistral VibeView original changelog

Mistral Vibe added a /goal command that sets an objective the agent keeps pursuing across turns until it is finished. Goals can be edited, paused, resumed and cleared, and a new max_goal_token_budget setting caps how many tokens a goal may spend.

Key Takeaways

  • /goal turns Vibe into a persistent worker, continuing across turns until the objective is complete.
  • Goals are fully manageable mid-run with edit, pause, resume and clear subcommands.
  • max_goal_token_budget in config.toml caps how many tokens a goal may spend.
  • The same setting acts as the default budget for goals set without one.
  • Pausing and resuming lets users step in without losing the objective.
  • The feature reduces repetitive re-prompting on long multi-step tasks.

A persistent objective for the agent

Mistral Vibe 3.1.3 introduced /goal <objective>. Instead of re-prompting after every turn, a user states what should be achieved and Vibe keeps working on it across turns until the goal is done. This suits long tasks such as migrations, test-suite repairs or multi-step refactors, where one prompt rarely finishes the job.

Managing a goal

A goal can be changed while it runs. /goal edit revises the objective, /goal pause and /goal resume stop and restart the work, and /goal clear removes the goal entirely. This gives users control over a long-running objective without ending the session.

Budget control

A goal that keeps working across turns can consume many tokens, so Mistral Vibe added the max_goal_token_budget option in config.toml. It caps the token budget any goal may set, and it also serves as the budget for a goal created without an explicit one. Teams can set a ceiling once and rely on it for every goal.