How an imported repo is cloned and decomposed into components and flows

When you import a public repository, it doesn't just drop in as a pile of files — it's cloned into your project and broken down into structured components and flows.

Clone into Documents

The import runs through your project's import endpoint, which clones the repository into a folder inside the current project's Documents. The folder keeps its nested structure, so paths in the imported tree match the original repo. In the IDE, those nested folders appear in the file tree just like the rest of your project — file keys can contain slashes to represent the directory layout.

Decompose into components and flows

After cloning, the import pipeline decomposes the repository into components and flows. This gives you more than a raw file dump: the imported project is represented in a way that fits into your project's canvas and flow model, so you can work with its pieces rather than just its files.

Working with the result

Once imported, everything behaves like normal project content. You can open and edit the files in the IDE, run the in-browser preview on runnable client-side web code, and ask Camelia to make changes across the folder. If the preview can't start because there's no entry point or there are broken imports, "Fix with Camelia" can make it runnable.

Scope note

The clone and decomposition happen inside the project you imported from — the repo becomes a folder in that project, not a separate project.