Where imported repositories land inside your current project

Importing a repository — whether from the Open Source Explorer or another import path — always adds it to the project you're already in. It never creates a separate project.

It lands in the current project

When you import a repo, it's cloned into a folder inside the current project's Documents and decomposed into components and flows. The Open Source Explorer always lives inside a project, so imports stay scoped to where you're working. The result is a new folder in that project rather than a fresh standalone project.

How it appears

The clone keeps its nested directory structure. In the IDE file tree you'll see it as a folder you can expand, with the original paths preserved — file keys can contain slashes to represent subfolders. From there the imported files behave like any other project content: editable in the IDE, previewable if they're runnable client-side web code, and available to Camelia for whole-folder edits.

If you want it in its own project

Because imports go into the current project, create or switch to the project you want it in before importing. That way the clone lands where you intend it to.

Tip for multiple imports

You can import more than one repository into the same project — each lands as its own folder under Documents, so they stay organized and don't overwrite each other.