CodePiler Docs
Uploading repositories
Import repositories into CodePiler with folder upload or ZIP upload, understand filtering behavior, and prepare clean source context for prompt generation.
Folder upload
Folder upload is ideal when the repository already exists locally. CodePiler reads file contents directly in the browser and preserves the directory structure for the tree explorer.
This mode is the fastest option during active development because there is no archive extraction step. After loading, CodePiler automatically pre-selects a focused set of source files to keep the initial token count manageable.
ZIP upload
ZIP upload works well for repositories downloaded from GitHub or shared as archives. CodePiler extracts the archive client-side and keeps the project grouped under a stable root path.
Common build artifacts, binary assets, caches, and oversized files are filtered automatically before they reach the viewer.
FAQ
Should I use folder upload or ZIP upload?
Use folder upload when you have the repository locally and want the simplest path. Use ZIP upload when the project arrives as an archive or when you want to share a self-contained snapshot.
Why are some files missing after upload?
CodePiler filters out common generated folders (node_modules, .git, dist, build), large files over 200 KB, binary assets, and non-source files to keep the workspace focused and prompt sizes manageable.
Can I upload multiple repositories?
Uploading a new repository replaces the current one. Save your session first if you want to come back to the current selection later.