Mistral Vibe: Commands Started With & Are Stopped When They Exit
Mistral VibeView original changelog
Mistral VibeOn macOS and Linux, anything a bash command or hook starts with & is now stopped when it exits. Long-running commands must go through background processes.
Key Takeaways
- Processes started with
&now stop when the command or hook exits. - It applies to
bashcommands and hooks on macOS and Linux. - Long-running work should use background processes.
- Workflows relying on orphaned dev servers may break.
- It prevents stray processes from outliving their command.
- It shipped in Mistral Vibe 3.1.1.
A behavior change
On macOS and Linux, processes started with & by a bash command or a hook no longer outlive it. When the command exits, they are stopped.
What to do instead
Long-running commands should use Vibe's background process mechanism. Workflows that relied on a trailing & to leave a dev server running will need adjusting.