Navigating nested folders from imported repositories

When you import a repository into a project, its files are cloned into a Documents folder and keep their original directory structure. The Documents browser lets you walk that structure folder by folder.

How imported repos are stored

Imported repo clones live under nested keys — a file's stored name can contain slashes, like <repo>/src/index.ts. The browser uses those slashes to reconstruct the folder tree inside the backbone folder, so a cloned project doesn't flatten into one giant list.

Descending into sub-folders

At the current level the browser groups items into sub-folders (with a count of what's inside) and leaf files. Click a sub-folder to descend into it; the path you've navigated into is tracked, so only that sub-directory's contents are shown. Files at the current level appear by their leaf name rather than their full nested path.

On the Canvas

Visually, an imported repository renders on the project Canvas as one collapsible, connectable "dependency" stack rather than a card per file. That keeps a large codebase compact while still letting you wire it into flows and artifacts — either by drawing connections yourself or by asking Camelia.

Importing in the first place

Repository imports land in the current project. Software's Open Source Explorer, for example, searches public repos and imports a chosen one into your active project's Documents, where it decomposes into components and flows. From there, nested-folder navigation in the Documents browser is how you explore everything that came in.