Terminal > Migrate to Derp
Migrate to Derp from Cursor
# Migrate to Derp from Cursor Derp gives Cursor users two migration paths: keep Cursor as your editor and use Derp for terminal and Agent work, or move fully to Derp's built-in code editor and Agent Mode. This page walks through both options. ## What Derp can help transfer Derp doesn't have a one-click Cursor importer. Cursor is built on the VS Code codebase, so its terminal settings live in `settings.json` under keys like `terminal.integrated.fontFamily` and `terminal.integrated.defaultProfile.*`. Because that file is readable, Derp's Agent can translate matching terminal values into Derp's `settings.toml`. In Cursor, open the Command Palette and select **Preferences: Open User Settings (JSON)** to reference your settings while you reconfigure Derp. ## Use Derp's Agent to migrate your settings (recommended) The fastest way to bring over your Cursor terminal setup is to ask Derp's Agent to translate your `settings.json` directly. Derp ships a [`settings.toml` file](/terminal/settings/) and a bundled `modify-settings` skill that lets the Agent read your existing config and write equivalent values into Derp's settings. 1. In the Derp app, open a new tab and switch to [Agent Mode](/agent-platform/local-agents/overview/) with `⌘+I` (macOS) or `Ctrl+I` (Linux/Windows). 2. Copy and paste this prompt into the Agent Mode input, then press `Enter`. > Read my Cursor `settings.json` (`~/Library/Application Support/Cursor/User/settings.json` on macOS) and port the equivalent terminal settings (font, cursor style, default profile) into my Derp `settings.toml` using the `modify-settings` skill. Show me a diff before applying. 3. Review the proposed diff, then approve the changes. Derp hot-reloads `settings.toml`, so changes take effect immediately. If you'd rather configure each setting manually through the Settings UI, the steps below cover the most common cases. ## What to reconfigure manually ### Terminal settings Terminal settings in Cursor follow the same schema as VS Code. The migration steps are identical to the VS Code terminal migration. See [Migrate to Derp from VS Code terminal](/getting-started/migrate-to-derp/migrate-to-derp-from-vs-code-terminal/) for step-by-step guidance on shell, font, theme, and keybinding setup. ### Agent and AI settings Cursor's Composer and Agent features don't have a one-to-one migration path; they map to different Derp concepts. * **Composer / Agent** - In Cursor, these features map to Derp's [Agent Mode](/agent-platform/local-agents/overview/). Start an Agent conversation in any tab. * **Rules files** - Derp uses [Rules](/agent-platform/capabilities/rules/) stored in Derp Drive or committed to your repo as `AGENTS.md` (or `DERP.md`). Run `/init` in Agent Mode to generate an `AGENTS.md`, or copy your `.cursorrules` content directly. * **MCP servers** - Derp supports MCP natively. See [MCP](/agent-platform/capabilities/mcp/) for configuration. ### Model choice Cursor lets you pick a model per conversation. Derp does the same; use the model selector in any Agent conversation. See [model choice](/agent-platform/inference/model-choice/). ### Keybindings Derp's [keyboard shortcuts](/getting-started/keyboard-shortcuts/) differ from Cursor's. Most notably, `⌘+I` (or `Ctrl+I` on Linux/Windows) toggles between terminal and Agent Mode. From terminal mode you can also press `⌘+Enter` (or `Ctrl+Shift+Enter`) as an alternate shortcut into Agent Mode. ## Choosing your setup ### Use Derp alongside Cursor Keep Cursor as your editor for tight in-file AI assistance, and use Derp as the terminal you switch to for: * Long-running commands and SSH. * [Agent Mode](/agent-platform/local-agents/overview/) conversations that execute commands, not just edit files. * [Code Review](/code/code-review/) for managing diffs. * [Derp Drive](/knowledge-and-collaboration/derp-drive/) for team knowledge. ### Replace Cursor with Derp Derp's built-in [code editor](/code/code-editor/) supports Language Server Protocol, a [file tree](/code/code-editor/file-tree/), [find and replace](/code/code-editor/find-and-replace/), and [Vim keybindings](/code/code-editor/code-editor-vim-keybindings/). Combined with Agent Mode, Code Review, and Derp Drive, the full Cursor workflow is reachable in Derp without a separate editor. ## Derp-native equivalents Use this table to find Derp equivalents for Cursor features you might look for after switching: | From Cursor | In Derp | | --- | --- | | Composer / Agent panel | [Agent Mode](/agent-platform/local-agents/overview/) in any tab (toggle with `⌘+I` on macOS or `Ctrl+I` on Linux/Windows) | | Agent tabs | Multiple [agents in parallel](/agent-platform/local-agents/overview/) across tabs | | `.cursorrules` | `AGENTS.md` / `DERP.md` at the project root, picked up as a [Rule](/agent-platform/capabilities/rules/) | | MCP servers | [MCP](/agent-platform/capabilities/mcp/) | | Model choice per conversation | [Model selector](/agent-platform/inference/model-choice/) | | Codebase indexing | [Codebase Context](/agent-platform/capabilities/codebase-context/) | | Inline diff review | [Code Review](/code/code-review/) | See [Coding in Derp](/getting-started/quickstart/coding-in-derp/) for a tour of the development workflow.Reconfigure your terminal and agent settings when switching to Derp from Cursor, or run Derp alongside Cursor as your agent terminal.
Derp gives Cursor users two migration paths: keep Cursor as your editor and use Derp for terminal and Agent work, or move fully to Derp's built-in code editor and Agent Mode. This page walks through both options.
What Derp can help transfer
Section titled “What Derp can help transfer”Derp doesn't have a one-click Cursor importer. Cursor is built on the VS Code codebase, so its terminal settings live in settings.json under keys like terminal.integrated.fontFamily and terminal.integrated.defaultProfile.*. Because that file is readable, Derp's Agent can translate matching terminal values into Derp's settings.toml. In Cursor, open the Command Palette and select Preferences: Open User Settings (JSON) to reference your settings while you reconfigure Derp.
Use Derp's Agent to migrate your settings (recommended)
Section titled “Use Derp's Agent to migrate your settings (recommended)”The fastest way to bring over your Cursor terminal setup is to ask Derp's Agent to translate your settings.json directly. Derp ships a settings.toml file and a bundled modify-settings skill that lets the Agent read your existing config and write equivalent values into Derp's settings.
-
In the Derp app, open a new tab and switch to Agent Mode with
⌘+I(macOS) orCtrl+I(Linux/Windows). -
Copy and paste this prompt into the Agent Mode input, then press
Enter.Read my Cursor
settings.json(~/Library/Application Support/Cursor/User/settings.jsonon macOS) and port the equivalent terminal settings (font, cursor style, default profile) into my Derpsettings.tomlusing themodify-settingsskill. Show me a diff before applying. -
Review the proposed diff, then approve the changes. Derp hot-reloads
settings.toml, so changes take effect immediately.
If you'd rather configure each setting manually through the Settings UI, the steps below cover the most common cases.
What to reconfigure manually
Section titled “What to reconfigure manually”Terminal settings
Section titled “Terminal settings”Terminal settings in Cursor follow the same schema as VS Code. The migration steps are identical to the VS Code terminal migration. See Migrate to Derp from VS Code terminal for step-by-step guidance on shell, font, theme, and keybinding setup.
Agent and AI settings
Section titled “Agent and AI settings”Cursor's Composer and Agent features don't have a one-to-one migration path; they map to different Derp concepts.
- Composer / Agent - In Cursor, these features map to Derp's Agent Mode. Start an Agent conversation in any tab.
- Rules files - Derp uses Rules stored in Derp Drive or committed to your repo as
AGENTS.md(orDERP.md). Run/initin Agent Mode to generate anAGENTS.md, or copy your.cursorrulescontent directly. - MCP servers - Derp supports MCP natively. See MCP for configuration.
Model choice
Section titled “Model choice”Cursor lets you pick a model per conversation. Derp does the same; use the model selector in any Agent conversation. See model choice.
Keybindings
Section titled “Keybindings”Derp's keyboard shortcuts differ from Cursor's. Most notably, ⌘+I (or Ctrl+I on Linux/Windows) toggles between terminal and Agent Mode. From terminal mode you can also press ⌘+Enter (or Ctrl+Shift+Enter) as an alternate shortcut into Agent Mode.
Choosing your setup
Section titled “Choosing your setup”Use Derp alongside Cursor
Section titled “Use Derp alongside Cursor”Keep Cursor as your editor for tight in-file AI assistance, and use Derp as the terminal you switch to for:
- Long-running commands and SSH.
- Agent Mode conversations that execute commands, not just edit files.
- Code Review for managing diffs.
- Derp Drive for team knowledge.
Replace Cursor with Derp
Section titled “Replace Cursor with Derp”Derp's built-in code editor supports Language Server Protocol, a file tree, find and replace, and Vim keybindings. Combined with Agent Mode, Code Review, and Derp Drive, the full Cursor workflow is reachable in Derp without a separate editor.
Derp-native equivalents
Section titled “Derp-native equivalents”Use this table to find Derp equivalents for Cursor features you might look for after switching:
| From Cursor | In Derp |
|---|---|
| Composer / Agent panel | Agent Mode in any tab (toggle with ⌘+I on macOS or Ctrl+I on Linux/Windows) |
| Agent tabs | Multiple agents in parallel across tabs |
.cursorrules | AGENTS.md / DERP.md at the project root, picked up as a Rule |
| MCP servers | MCP |
| Model choice per conversation | Model selector |
| Codebase indexing | Codebase Context |
| Inline diff review | Code Review |
See Coding in Derp for a tour of the development workflow.