Skip to main content
vibld
Sign up for the beta
Menu

← All guides

Using vibld

Data portability

Checked against the product on

Everything a vibld project is made of, and how to get each part out. This page describes the exports as they work today. It does not say which law applies to them; the Privacy Policy covers your rights over your information.

At a glance

WhatHow it comes outFormat
The project’s codeDownload .zip, Push to GitHub, the API, the MCP serverZip archive, a Git commit, JSON
Earlier checkpointsThe API and the MCP serverJSON
Images and video you uploadedPush to GitHub (the ones the code uses), the APIThe files as uploaded
The conversation and the project’s settingsThe APIJSON
Your plan and billingThe billing portal, the APIStripe’s portal, JSON

The code

A project is ordinary source: a Vite and React app with a package.json, a README.md that says how to run and build it, and a DESIGN.md when the build wrote a spec. There is no vibld runtime in it. A project may carry a .vibld/ folder of build metadata; nothing else in the project uses it, so deleting it breaks nothing. Four ways to take it, each reading the last accepted checkpoint:

  • Download .zip, under Ship. The archive is made in your browser, from the checkpoint’s files exactly as they are, and named vibld-<revision>.zip. It holds the code only: no history, no conversation, no media.
  • Push to GitHub, under Ship. One commit on a branch named vibld/<revision> and a pull request against the repository’s default branch, in a new repository on your GitHub account or an existing one you can push to, an organization’s included. It is one way: vibld does not read code back from GitHub. Taking your code with you has the details.
  • The API. GET /api/projects/{id}/files answers with every file as {path, content} JSON. See The builder API.
  • The MCP server at app.vibld.com/mcp. list_files and read_files read the same files from an assistant you connect, once you approve editing.

Checkpoints

Every accepted build, repair, edit and restore is a checkpoint. GET /api/projects/{id}/checkpoints lists the newest 100, and GET /api/projects/{id}/files with ?revision= reads any of them, as list_checkpoints and read_files do over MCP. Older checkpoints, and versions a run produced that were never accepted, have no export.

Images and video

Files you upload to the media library are kept as uploaded (JPEG, PNG, GIF, WebP, AVIF, MP4 or WebM).

  • A push to GitHub adds the ones the code uses as public/media/<name>, up to 12 MB a file and 32 MB a push. The push names any file it left out.
  • GET /api/media lists the library, and GET /api/media/file?path= answers with one file’s bytes.
  • The .zip download does not include media.

The conversation and settings

GET /api/projects/{id} answers with the project’s conversation (each message, what the builder said back, and the checkpoint it produced) and its settings, including standing instructions and style choices, as JSON. Neither is in the .zip, the push or the MCP server.

Builds

GET /api/runs?project= lists a project’s last 20 runs: model, tokens, cost, how each ended and how long it took. Detailed build logs have no export.

Your account

  • Billing. Manage billing opens Stripe’s billing portal for your subscription and payment method; GET /api/billing/status answers with your plan and this period’s spend.
  • Referrals. GET /api/referral/status answers with your code and what it has earned.
  • Deleting your account. Content is purged 30 days after you ask. Until then you can cancel, but every other request is refused, exports included, so take what you want first.
  • Anything else. There is no single download of a whole account. The Privacy Policy says how to ask for a copy of your information.