InteractiveOpen

Desktop editor

Move from VS Code

The files usually need no conversion; migration means choosing which editor/runtime capabilities to reproduce.

Typical migration: Easy · Best method: Local folder · Git · ZIP

Before You Move

  • Save/commit the project.
  • List essential VS Code tasks/extensions/settings.
  • Identify environment variables and local tool dependencies.

Migration Steps

  1. 1. Open project — Link folder, clone Git or import ZIP.
  2. 2. Runtime — Use the Interactive Terminal when cloud execution is useful.
  3. 3. Map workflow — Use project scripts and built-in capabilities for the VS Code tasks/extensions that matter.
  4. 4. Verify — Run build/test/preview commands.

Where Things Go

VS Code workspaceInteractive Shell project
Integrated terminalInteractive Terminal
TasksProject run/build commands
Source controlGit workflow

Verify

  • Files and language modes are correct.
  • Build/test succeeds.
  • Required editor-only features have an alternative.

Common Issues

  • Extensions — VS Code extensions do not automatically migrate.
  • Workspace settings — Settings can remain in source but Interactive Shell may not interpret VS Code-specific keys.

Last reviewed 2026-09-07.