v0.9.17
Changes in v0.9.17
Fix: Mistral/Vibe provider stuck in onboarding TUI loop
The Vibe provider's isolated VIBE_HOME setup had two bugs that caused Vibe to show its animated "Welcome to Mistral Vibe - Let's get you started!" onboarding screen in an infinite loop instead of running tasks:
-
Wrong auth files symlinked: The code tried to symlink
state.jsonandconfig.yaml— neither of which exist in~/.vibe/. The correct files are.env(Mistral API key),config.toml, andtrusted_folders.toml. Without.env,VibeConfig.load()throwsMissingAPIKeyErrorwhich triggers Vibe's interactive onboarding TUI. -
VIBE_HOME pointed one directory too high:
setupIsolatedHome('.vibe', ...)places symlinked files atisolatedHome/.vibe/, butVIBE_HOMEwas set toisolatedHome(the parent). Vibe then looked forconfig.tomlatisolatedHome/config.tomlwhich didn't exist. Fixed by settingVIBE_HOME = isolatedHome + '/.vibe'.
Also fixes session log extraction to scan the correct vibeHome path instead of isolatedHome.
Full changelog: v0.9.16...v0.9.17