Mistral Vibe: Pull Request Tracking Is Now On by Default With Clearer Footer Status

Mistral VibeView original changelog

Session pull and merge requests are now tracked by default (with gh or glab). The footer names the cause (CI failing, changes requested, conflicts, CI running, review required). enable_pr_monitoring = false turns it off, and the old experimental settings are ignored.

Key Takeaways

  • PR/MR tracking is enabled by default and relies on gh or glab.
  • Opt out with enable_pr_monitoring = false.
  • The footer shows why a PR is blocked, such as CI failing or review required.
  • The open PR is preferred over merged or closed ones.
  • Duplicate PR entries are gone and multi-PR commands record all PRs.
  • The experimental settings are removed in favor of enable_pr_monitoring.

On by default

Mistral Vibe 3.1.1 tracks a session's pull and merge requests by default, using gh or glab. To opt out, set enable_pr_monitoring = false or VIBE_ENABLE_PR_MONITORING=false.

Clearer footer status

The footer's PR/MR status now names its cause: CI failing, changes requested, conflicts, CI running or review required. It prefers the open PR over merged or closed ones, and reads bold until a new status has been seen.

Cleanup

The experimental_enable_pr_monitoring and experimental_enable_pr_discovery settings and the VIBE_EXPERIMENTAL_ENABLE_PR_MONITORING variable are removed and ignored. The same PR no longer shows twice in the footer list, and a command creating several PRs/MRs now records all of them.