Export formats
What leaves REM Vibe Coder and in which form - the code zip, the app's repository and branches, the generated README, the app layout, and documents.
The code zip
GET /api/v1/projects/{id}/code.zip (or Download code (.zip) in the Code pane), owner or admin only.
Name |
|
Contents | Exactly the app's files (the same filter as the git push) plus one generated |
Left out |
|
Size limit | 200 MB of staged files (answer |
Delivery | Streamed file by file; nothing is kept on disk |
The file list is the same as GET /projects/{id}/files; GET /projects/{id}/file?path=… returns one file and answers 404 for any path the filter leaves out.
Layout of a typical app
The default stack is a FastAPI API with a React front end built with Vite:
Path | What |
|---|---|
| The API (FastAPI), its routes and models |
| Unit and API tests (pytest) |
| The web app (React, Vite) |
| Browser workflow tests (Playwright) |
| Generated: what the app is and how to run it |
Other shapes exist when the request calls for them: an MCP server (server.py, requirements.txt), scheduled jobs (jobs.toml plus the job scripts), or an app on the Aurora admin template.
The generated README
Written for the zip and the repository, with generic commands only (no platform names, deploy commands, internal addresses or tokens):
a table of the folders that exist in this app;
if the app keeps data: set
DATABASE_URLto a PostgreSQL URL first (the example has no credentials in it);create a virtual environment and install the API, run its tests, start it;
install and start the web app;
run the Playwright workflow tests, pinned to the version the build used.
The git repository
Each project's code is pushed to its repository in REM CloudHub through REM CloudHub's git service:
Branch | Holds |
|---|---|
| The first deployed version (merged through a pull request after the deploy was verified; fast-forward only) |
| A build with a ticket key, e.g. |
| Builds without a ticket: the first, then each change |
History is never rewritten and nothing is force-pushed. The README in the repository is the same as in the zip, and no file contains a credential (REM CloudHub's push check refuses URLs with credentials in them).
Documents
Documents are written as Markdown and kept in REM CloudHub's docs (the project's private space, with versions). On request REM CloudHub converts them to DOCX, PDF or XLSX and stores those in the chat's Files folder (vibecoder/chats/<chat>). Vibe Coder has no converter of its own, so the files are the same as any other REM CloudHub conversion.
Data
A deployed app's data lives in its PostgreSQL database in REM CloudHub (DATABASE_URL and DB_SCHEMA are given to the app at start). Export it from the database's page in REM CloudHub; Vibe Coder itself only reads the schema and runs read-only queries when you ask about your data.