Migrating from Cline
Dline does not import Cline data on its own. It starts with empty Dline folders and never reads, modifies, or deletes Cline files. If you want to keep your Cline configuration, copy it into Dline’s folders by hand as described below.
Before you start
Section titled “Before you start”- Close every VS Code window, so neither Cline nor Dline is writing its files while you copy.
- Find the folders on your machine.
<Documents>is the operating system’s Documents directory.
| Folder | Cline | Dline |
|---|---|---|
| Data root: settings, global state, secrets | ~/.cline/data/ | ~/.dline/data/, or <DLINE_DIR>/data/ when DLINE_DIR is set |
| Documents root: rules, workflows, skills, hooks, MCP | <Documents>/Cline/ | <Documents>/dline/, or the folder in DLINE_DOCS_DIR when it is set |
| Endpoint configuration | ~/.cline/endpoints.json | ~/.dline/endpoints.json |
See Configuration for what these variables control.
What you can copy
Section titled “What you can copy”| What | Copy from | Copy to |
|---|---|---|
| Settings, global state, and stored credentials | the contents of ~/.cline/data/ | the Dline data root |
| Endpoint configuration | ~/.cline/endpoints.json | ~/.dline/endpoints.json |
| MCP servers | <Documents>/Cline/settings/cline_mcp_settings.json | settings/mcp_settings.json in the Dline documents root (note the new file name) |
| Global rules, workflows, skills, and hooks | the matching folders in <Documents>/Cline/ | the matching folders in the Dline documents root |
Dline’s global folder names are lowercase: rules/, workflows/, skills/, hooks/, mcp/. On a case-sensitive file system, rename a Cline folder whose casing differs, such as Rules, to the lowercase name.
What cannot be carried over
Section titled “What cannot be carried over”- Task history. Do not copy
<Documents>/Cline/tasks/or the task records in Cline’s extension storage. Dline indexes tasks in SQLite and keeps per-task runtime state that a Cline task directory does not contain, so Cline tasks cannot be opened or resumed in Dline. - Checkpoints, browser data, and caches. They belong to Cline tasks and are rebuilt by Dline as needed.
After copying
Section titled “After copying”- Start VS Code and open Dline.
- Open the provider settings and confirm your configuration is there.
- Open the MCP server settings and confirm your servers are listed. See MCP overview.
- Check that your global rules and workflows are visible in Dline.
Your Cline files stay where they are, so you can keep using Cline next to Dline.