Move to Interactive Shell

Migration Guides

• Move from Replit — Bring a Replit project into Interactive Shell without turning the migration into a rewrite.
• Move from Cursor — Cursor projects are ordinary files, so the source move is usually simple; the main transition is editor, runtime and AI configuration.
• Move from CodePen — Turn a Pen into a portable multi-file project you can continue with a full IDE and Linux runtime.
• Move from CodeSandbox — Most ordinary web projects migrate cleanly when the repository/package manifests are complete.
• Move from StackBlitz — Keep the web project but move execution from browser WebContainers to an optional real Linux environment.
• Move from GitHub Codespaces — The repository is already the durable project source; migration mainly means translating environment configuration.
• Move from Windsurf — Source migration is usually straightforward; focus on the AI and runtime workflow you want afterward.
• Move from Bolt — Keep the generated app, then move from prompt-first building into a complete development workflow.
• Move from Lovable — Take ownership of the generated source and continue development with normal project tools.
• Move from Gitpod — The repository remains the durable source; translate workspace automation instead of copying an ephemeral environment.
• Move from VS Code — The files usually need no conversion; migration means choosing which editor/runtime capabilities to reproduce.
• Move from Overleaf — Bring the complete LaTeX project into Interactive Shell while keeping ordinary source files and compiler control.
• Move from Jupyter — Bring the scientific project intact while being explicit about notebook UI versus script/runtime workflows.