YOLO Studio
AgentsGuidesDocsHome

Guide

Move a local project into a cloud workspace for your coding agents

Your project lives on your laptop, but you want Claude Code, Codex or Gemini CLI working on it in a sandbox that keeps going when you close the lid. yolostart brings the project into a YOLO Studio workspace with one command, and nothing uploads until you approve the list.

Get started

Why move it at all

Agents keep working

The agent runs in the cloud workspace, not on your laptop, so closing the lid or the browser tab does not stop it.

Room for several agents

Each agent can work in its own lane, a separate git clone on its own branch, so two agents never edit the same working copy.

A sandbox, not your laptop

Every workspace is a secure Linux sandbox running in its own virtual machine. The agent works on your repository inside it, as a non-root user, with your files kept between sessions. It cannot reach your laptop, your other projects or anyone else’s workspace.

Import it with yolostart

  1. 01

    Run it from your project folder

    curl -fsSL https://yolostart.sh | sh

    The installer downloads yolostart, checks its checksum and runs it. With Node 20 or later, npx yolostart@latest does the same. It needs no sudo, and Git is required to detect repositories.

    yolostart.sh

  2. 02

    Sign in

    yolostart opens a sign-in link in your browser. Approve the sign-in there.

  3. 03

    Review what would upload

    yolostart scans the project on your machine and sends only file paths, counts and sizes. The approval page lists what would upload: untick anything you want to leave behind, name the workspace, then choose Approve & upload.

  4. 04

    Open the workspace

    yolostart packs exactly the files you approved, uploads them and prints the workspace link once your project is in. Add an agent tile and give it its first job.

What stays on your machine

Secrets

Files that look like secrets, such as .env files, private keys, .aws, .ssh and credential JSON files, are never uploaded, even if you ask. Add the secrets your app needs to the workspace yourself.

Dependencies and build output

node_modules, dist, build, .next, target and similar folders stay behind, along with anything your .gitignore excludes. Install dependencies in the workspace.

Your project on disk

yolostart reads your project and changes nothing in it. Your sign-in is kept in memory only, never written to disk.

Git history comes along when it is 25 MB or smaller, and it is not scanned, so a secret that was ever committed travels with it. Rotate any secret that was ever committed before you import.

Questions

Can I see what would upload without uploading anything?

Yes. yolostart --dry-run signs in, scans, and prints what would be imported as JSON, without creating an import. Through the shell installer, run curl -fsSL https://yolostart.sh | sh -s -- --dry-run.

My project is already on GitHub. Do I need yolostart?

No. You can create a workspace from a GitHub repository directly. yolostart is for projects that live only on your machine, or that you want to bring over as they are right now, including changes you have not committed.

How big can a project be?

An import can be up to 100 MB compressed, 1 GB uncompressed and 20,000 files. Files over 25 MB, symbolic links and nested repositories are left out. Each import counts as one of your plan’s workspaces.

Keep reading

yolostart.shDocs: yolostartGuide: connect a local coding agentCloud vs local coding agentsRun Claude Code in the cloud

Try it on your own repository

Sign in with GitHub, open a workspace on your repository, and put your first agent to work in a few minutes.

Get started
YOLO Labs

© 2026 Yolo Labs, LLC

HomeSecurityDocs