Migrate
Your chats come through the JSON importer, and the split-view habit maps straight onto parallel model tabs.
Launching soon: this surface is rolling out
| Msty | In idapt | How |
|---|---|---|
| Chats (JSON export) | Chats via the universal chat-JSON importerMsty's export is JSON-family; map it to the documented shape (a small transform). | Automatic |
| The split-view comparison habit | Model tabs: one prompt, several models side by sideNo data to move: it is how idapt chat already works. | Automatic |
| Local models (Ollama) | Local AI via your paired computerIf you already run Ollama, pair that machine; idapt discovers its models. | Manual |
| Provider API keys | BYOK provider connections in the Gateway tab | Manual |
Export your conversations as JSON from Msty's settings or data folder.
Settings → Import → "Other apps (JSON)". The help article documents the chat-JSON fields if the export needs a transform.
Send one prompt, then add model tabs to read several models' replies side by side. Pair your Ollama machine and local models join the same picker.
Connect your own provider keys (OpenAI, Anthropic, OpenRouter, Google AI Studio, xAI, DeepSeek, and more) and matching calls bill straight to your provider account instead of idapt credits. Local models run free via Ollama on your paired computers. Your existing spend comes with you. Nothing is locked to ours.
Yes. Model tabs run the same prompt across several models with shared context, so the split-view habit transfers without the desktop app.
Pair the machine that runs Ollama and idapt routes to it as a free local provider; cloud models sit in the same picker for the jobs that outgrow it.