Migration
If you’re coming from another AI coding agent, the /migrate command reads your existing configuration and imports it into Caboose. It scans for MCP servers, system prompts, and project instruction files, presents them in a toggle checklist, and applies only what you select.
Supported sources
Section titled “Supported sources”| Tool | What gets imported |
|---|---|
| Claude Code | MCP servers from ~/.claude/, CLAUDE.md project instructions, system prompt |
| Open Code | MCP servers, system prompt |
| Codex | MCP servers, system prompt, AGENTS.md project instructions |
Running the migration
Section titled “Running the migration”/migrateCaboose scans for configuration files from all supported tools and presents a checklist:
Found configuration from: Claude Code, Codex
[x] MCP server: context7 [x] MCP server: github [ ] System prompt (154 tokens) [x] Project instructions: CLAUDE.md → .caboose/instructions.md
Apply selected? [Enter to confirm]Toggle items with Tab, then press Enter to apply. A preview of each item is shown before you confirm.
What happens after migration
Section titled “What happens after migration”- MCP servers are added to your global config (
~/.config/caboose/config.toml) - System prompts are saved as a custom system prompt in your global config
- Project instructions are copied to
.caboose/instructions.mdin your project root
Nothing from your original tool’s config is modified or deleted — migration is always additive.