---
title: "Configuration Import"
description: "Control how Devin for Terminal imports settings from Cursor, Windsurf, and Claude Code"
icon: "arrow-right-to-bracket"
---

Devin for Terminal can automatically import rules and configuration from other AI coding tools installed in your project. This happens when configuration files from Cursor, Windsurf, or Claude Code are detected in your workspace.

---

## How It Works

When you start a session, Devin for Terminal checks for configuration files from supported tools and imports what it finds.

### Cursor

| What's imported | Source files |
|----------------|-------------|
| Rules | `.cursorrules`, `.cursor/rules/*.md`, `.cursor/rules/*.mdc` |
| MCP servers | `.cursor/mcp.json` |

### Windsurf

| What's imported | Source files |
|----------------|-------------|
| Rules | `.windsurf/rules/*.md`, `.windsurf/global_rules.md` (at workspace root and subdirectories) |
| Skills | `.windsurf/skills/` (project), `~/.codeium/<channel>/skills/` (global, channel-dependent) |
| Workflows | `.windsurf/workflows/*.md` |
| MCP servers | `~/.codeium/<channel>/mcp_config.json` (channel-dependent) |

<Note>
Devin for Terminal reads from the Windsurf config directory matching its own channel: stable reads from `~/.codeium/windsurf/`, next reads from `~/.codeium/windsurf-next/`, insiders reads from `~/.codeium/windsurf-insiders/`. `.windsurf/rules/` directories can exist at multiple levels in your project. Rules at the workspace root are loaded at session start. Rules in subdirectories are discovered lazily when the agent accesses files in that directory.
</Note>

### Claude Code

| What's imported | Source files |
|----------------|-------------|
| Rules | `CLAUDE.md`, `~/.claude/CLAUDE.md` |
| Skills | `.claude/skills/**/SKILL.md` |
| Commands (as skills) | `.claude/commands/**/*.md` |
| MCP servers | `.mcp.json`, `.claude/settings.json`, `.claude/settings.local.json`, `~/.claude.json`, `~/.claude/settings.json`, `~/.claude/settings.local.json`, `~/.claude/mcp_servers.json` |

---

## Disabling Configuration Import

To stop importing from a specific tool, set it to `false` in your config:

<Tabs>
  <Tab title="User config">
    ```json
    // ~/.config/devin/config.json
    // (on Windows: %APPDATA%\devin\config.json)
    {
      "read_config_from": {
        "cursor": false,
        "windsurf": false,
        "claude": false
      }
    }
    ```
  </Tab>
  <Tab title="Project config">
    ```json
    // .devin/config.json
    {
      "read_config_from": {
        "windsurf": false
      }
    }
    ```
  </Tab>
</Tabs>

You can disable imports selectively — for example, import from Cursor but not Windsurf:

```json
{
  "read_config_from": {
    "cursor": true,
    "windsurf": false
  }
}
```

---

## Options

| Option | Type | Default | Description |
|--------|------|---------|-------------|
| `cursor` | boolean | `true` | Import rules and MCP servers from Cursor config files |
| `windsurf` | boolean | `true` | Import rules, skills, workflows, and MCP servers from Windsurf |
| `claude` | boolean | `true` | Import rules, skills, commands, and MCP servers from Claude Code |

Setting a value to `true` (or leaving it unset) enables import. Setting it to `false` disables import for that tool.

---

## Default Behavior

If you don't explicitly configure `read_config_from`, all imports are enabled by default. Set any option to `false` to disable imports from that tool.
