AI editor
Move from Cursor
Cursor projects are ordinary files, so the source move is usually simple; the main transition is editor, runtime and AI configuration.
Typical migration: Easy · Best method: Local folder · Git · ZIP
Before You Move
- Ensure the local folder or Git repository is current.
- Record any project-specific editor tasks/settings you actually depend on.
- Decide whether you want Ollama local models or BYOK cloud AI in Interactive Shell.
Migration Steps
- 1. Open project — Link the same local folder on a supported browser, clone Git, or import ZIP.
- 2. Runtime — Open the Interactive Terminal and install project dependencies if cloud execution is useful.
- 3. AI — Configure Ollama or BYOK providers as desired.
- 4. Verify — Run, build, test and preview the project.
Where Things Go
| Cursor workspace | Interactive Shell project |
|---|
| Integrated terminal | Interactive Terminal |
|---|
| Agent/Composer workflows | Interactive AI / AI Agents |
|---|
| Desktop local execution | Local project + optional Ubuntu runtime |
|---|
Verify
- Files open correctly.
- Language mode is correct.
- Dependencies install in the selected runtime.
- Build/test commands succeed.
- AI provider settings are intentionally configured.
Common Issues
- Extensions — Cursor/VS Code extensions do not automatically migrate. Use built-in capabilities or project dependencies where appropriate.
- Editor rules — Project instruction files may remain source files, but automatic behavioral compatibility is not promised.
Last reviewed 2026-09-07.