Migrate from Claude Code
Keep your setup, lose the lock-in. Claudin imports your existing configuration on first launch — then runs on any LLM provider.
Overview
Claudin originated from the Claude Code codebase and has been substantially modified to support any provider. Because of that shared lineage, moving over is not a fresh setup — it is an import. On its first launch, Claudin detects your existing ~/.claude/ directory and brings your configuration across automatically.
No export step. No config files to copy. No workflow to relearn.
# install claudin
npm install -g @claudiolabs/claudin@latest
# run — migration happens automatically on first launch
claudin
✓ Migrated settings from ~/.claude/
✓ Tokens, theme, plugins restored
✓ Ready — switch provider with /provider
What gets migrated
On first launch Claudin reads your Claude Code directory and carries over:
| What | Migrated |
|---|---|
| Auth tokens & API keys | Restored and ready to use |
| Settings | Your settings.json preferences are preserved |
| Theme | Your terminal theme carries over |
| Plugins | Installed plugins are restored |
| Keybindings | Your custom key map is preserved |
| Memory | Project and user memory come with you |
How it works
- Install Claudin. Requires Node.js 20+. Install globally with
npm install -g @claudiolabs/claudin@latest(orbun,npx, and the one-linecurlinstaller — see Install). - Run
claudin. On the very first launch it looks for~/.claude/. If it finds one, the migration runs before you reach the prompt — no flag required. - Start coding. Everything you configured in Claude Code is already in place. The only new thing is that you can now point Claudin at any model.
After you migrate
The reason to switch is provider freedom. Once your settings are imported, use the /provider wizard to add or switch models at any time — no environment variables, no restarts:
/provider # add, edit, or switch provider profiles
/provider doctor # health check: reachability, auth, model availability
You keep the full agentic workflow — bash, files, grep, glob, sub-agents, MCP, web search — but now on Anthropic, OpenAI, Gemini, DeepSeek, Mistral, Ollama, AWS Bedrock, Google Vertex, OpenRouter, Groq, or any of 200+ OpenAI-compatible endpoints. Prefer to stay fully offline? Pull a model with Ollama or LM Studio and run with no API key at all (see Local models).
Nothing is overwritten
Migration is a read, not a move. Claudin reads from ~/.claude/ and writes its own configuration to ~/.claudin/. Your original Claude Code directory is left untouched, so you can keep both tools installed and fall back at any time — the migration just gives Claudin a running start.
FAQ
Is migrating automatic?
Yes. On first launch Claudin detects your existing ~/.claude/ directory and migrates your tokens, settings, theme, plugins, keybindings, and memory. There are no manual export or import steps — just install and run.
Does it change or delete my Claude Code setup?
No. Claudin reads from ~/.claude/ and stores its own config in ~/.claudin/. The original directory is left in place, so both tools can coexist.
Can I use a provider other than Anthropic after migrating?
Yes — that is the point. After your settings import, run /provider to add or switch to OpenAI, Gemini, DeepSeek, Mistral, Ollama, AWS Bedrock, Google Vertex, OpenRouter, Groq, or any of 200+ OpenAI-compatible endpoints, without changing your workflow.
Is Claudin affiliated with Anthropic or Claude Code?
No. Claudin is an independent project. It is not affiliated with, endorsed by, or sponsored by Anthropic.