Repository coding in the cloud (pilot)

Updated 27 September 2026 · 2 min read

Hosted workspace owners can pick one GitHub repository in Preview. The workspace remembers that repository. A different repository needs a different workspace. Invited collaborators cannot publish under the owner's GitHub connection.

How a coding turn runs

When the pilot is switched on, repository conversations run in a short-lived Vercel Sandbox. The server downloads a pinned archive of the repository and hands the sandbox the files only. The sandbox never receives GitHub, Vercel or model credentials.

Commands run inside the sandbox. A checkpoint is saved after each completed command, so an interrupted command can lose the edits made since the last checkpoint.

Review, then publish

The review panel shows the full new contents of every changed file, with deletions marked. Commit & open PR publishes exactly what you reviewed to a task branch and opens or updates a pull request. It never merges and never deploys.

Pilot limits

Each worker has one CPU, a five-minute lifetime, no public ports and no outbound network. Installing packages from the network does not work.
The pilot allows ten worker starts in total, not per day.
Repository archives up to 32 MiB. Reviews up to 100 files or 4 MiB. Command output up to 32 KiB per stream.
Live web previews, side-by-side diffs and coding activity inside the chat transcript are not part of the pilot.

This is not a complete hosted IDE. Coding stays switched off in production until a dedicated credential and a real owner-authorized test are in place.