> For the complete documentation index, see [llms.txt](https://help.genesis.autify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.genesis.autify.com/resources-context/codebase.md). # Codebase This article explains the **Codebase** feature in the **Resources and Context** tab. By archiving source code as a ZIP file and uploading it, you can register source code in a workspace so the AI can reference code content when answering questions or running workflows. For GitHub integration, see [GitHub integration](/resources-context/github-integration.md). ## Prerequisites | Action | Required role | | ---------------- | ------------- | | Upload ZIP files | All members | | Delete codebase | Admin / Owner | ## Uploading as a ZIP file
Screenshot of the codebase upload area

Codebase upload area

1. On the workspace page, select the **Resources and Context** tab. 2. Select **Codebase**. 3. Drag and drop a ZIP file into the upload area, or click the area to choose a file. 4. Upload progress is shown as a percentage. After upload, indexing starts automatically. 5. When the status changes to **{n} indexed**, the codebase is available. {% hint style="info" %} The only supported format is ZIP (`.zip`). Limits: ZIP file up to 200 MB, total extracted size up to 5 GB, and up to 100,000 files in the archive. {% endhint %} {% hint style="info" %} Uploading a ZIP file consumes AI usage. Uploads are blocked when the usage limit is reached. A warning appears when storage usage reaches 80% of the limit, and new uploads are disabled when the limit is exceeded. {% endhint %} ### Supported file formats The following file extensions are included in indexing: **Code files**: `.ts` / `.tsx` / `.js` / `.jsx` / `.py` / `.go` / `.java` / `.rb` / `.rs` / `.c` / `.h` / `.cpp` / `.hpp` / `.cc` / `.cxx` / `.cs` / `.kt` / `.kts` / `.swift` / `.php` / `.sh` / `.sql` **Config and document files**: `.yml` / `.yaml` / `.toml` / `.json` / `.md` / `.txt` Directories such as `node_modules/`, `.git/`, `dist/`, and `build/`, along with test files and lock files, are automatically excluded. ### Indexing status | Status | Description | | ------------------------------ | ------------------------------------------------------------------------------ | | Ready | Extraction is complete. | | Queued for indexing | Waiting for indexing to start. | | Indexing ({processed}/{total}) | Files are being analyzed and indexed. The processed/total file count is shown. | | {n} indexed | Indexing is complete and the codebase is available. | | Indexing failed | An error occurred during indexing. | | Failed | An error occurred during upload or extraction. | ## Deleting a codebase Delete a codebase registered as a ZIP archive. To delete a codebase from a GitHub repository, see [GitHub integration](/resources-context/github-integration.md). 1. On the workspace page, select the **Resources and Context** tab. 2. Select **Codebase**. 3. Click the **menu** () at the right end of the codebase you want to delete. 4. Click **Delete**. ## Troubleshooting ### Upload errors | Error message | Resolution | | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Please upload a .zip file | Compress your source code as `.zip` before uploading. | | File size exceeds maximum allowed size of 200MB | Recreate the ZIP excluding unnecessary directories such as `node_modules/` and `dist/` so the archive stays within 200 MB. | | Failed to fetch | Reload the page and upload again. | | Storage limit exceeded | Your organization's storage is at the limit. Free up space by deleting unused codebases. If you need a higher limit, contact your organization Admin or Owner. | | Usage limit reached. Contact your administrator to increase the limit. | Your organization has reached its AI usage limit. Contact your organization Admin or Owner. | ### Extraction errors When the status becomes **Indexing failed** or **Failed** after upload, the following causes are possible. Delete the codebase once, fix the ZIP based on the cause, and upload it again. | Cause | Resolution | | ------------------------------------------------------------------------ | -------------------------------------------------------------------------------- | | ZIP contains more than 100,000 files | Exclude test and cache files and recreate the ZIP with fewer than 100,000 files. | | ZIP contains individual files larger than 200 MB | Exclude the large files and recreate the ZIP. | | Total extracted size exceeds 5 GB | Split the codebase or exclude unnecessary files and recreate the ZIP. | | ZIP created with a Windows tool includes drive letters (`C:\` and so on) | Recreate the ZIP in Unix/Linux or with a standard ZIP tool. | | ZIP contains symbolic links | Replace symlinks with actual files and recreate the ZIP. | ### Indexing errors | Situation | Cause | Resolution | | ------------------------------------------------ | ---------------------------------- | ------------------------------------------------------------------------------------- | | Status stays at **Indexing failed** | An error occurred during embedding | Delete the codebase and upload it again. If this happens repeatedly, contact support. | | **Queued for indexing** persists for a long time | The processing queue is congested | Wait and check again later. If the issue does not clear, contact support. |