Switching to Mistral Vibe? Bring your history with you
Months of Claude Code and Codex sessions sit in folders Vibe can’t read. The kcap local edition imports them into one timeline on your own machine, so Vibe can search them from its first prompt
Read the script
You’ve spent months with Claude Code and Codex. Hundreds of coding agent sessions. Every bug you chased, every decision, every fix that didn’t work. Now you want to try Mistral Vibe. But each coding agent keeps its history in its own folder, in its own format. Switch agents, and all of that stays behind. Vibe starts without it.
Here’s how to bring it with you, with the local edition of the kcap desktop app. Open the app, and choose: for you, locally. kcap installs its server on your own machine. No cloud workspace. Your sessions are stored right here. And search by meaning runs locally too, with a built-in model, or with Ollama.
Next, your coding agents. kcap finds the ones on this machine: Claude Code, Codex, Cursor, Gemini, and Mistral Vibe. Pick them, and kcap records each one from now on.
Then, your history. kcap finds the past sessions every agent left on disk, grouped by repository. Untick anything you’d rather keep out, and import. Claude Code and Codex, side by side, in one timeline.
Now open Vibe. Setup already gave it kcap’s tools. So ask it: how did we fix the webhook retries last month? Vibe searches your history, finds the Codex session where you fixed it, and reads back what actually happened. The fix that failed, the one that worked, and why.
And from now on, every Vibe session is recorded too. Same timeline, same search. Next time you switch, your history comes with you again. Your coding agents will change. Your history shouldn’t stay behind.
Three steps
then ask Vibe about last month
Setup gives Vibe kcap’s tools. Ask how you fixed something and it finds the session: the fix that failed, the one that worked, and why
Run kcap on your own machine
Open the desktop app and choose For you, locally. The server runs here, with no cloud workspace, and search by meaning runs locally too, on the built-in model or Ollama
Pick your coding agents
kcap finds the agents on this machine, from Claude Code and Codex to Cursor, Gemini and Mistral Vibe, and records each one you pick from then on
Import your history
Past sessions come grouped by repository. Untick anything you’d rather keep out, then import: every agent’s work lands side by side in one timeline
Switch again whenever you like
kcap records each of these, so your history follows you to the next one
