Skip to Content
Getting StartedOverview

Getting Started

Here’s how to get started with YOLO Studio. A workspace is a cloud that pairs a tiled UI (terminals, agents, previews, watchers, agent ) with a dedicated container where agents read your repo, write code and push branches, and you review what they produce.

Prerequisites

  • A YOLO Studio account — sign up at yolo.studio 
  • A way to sign in — GitHub is the primary method; Google is also available where enabled. See Sign-in & Git Providers for the full list.
  • (Optional) A GitHub account if you want to clone and push your own GitHub repositories. You can also host repositories inside YOLO with YOLO Internal Git — no external account required.

Sign in

  1. Go to yolo.studio  and choose a sign-in method:
    • Sign in with GitHub — the default. Signing in with GitHub also connects your GitHub account so you can clone and push your repositories.
    • Sign in with Google — available where enabled, if you’d rather not use GitHub to sign in.

For details on each method, on hosting repositories inside YOLO with YOLO Internal Git, and on Sign in with YOLO (single sign-on for the internal git web UI), see Sign-in & Git Providers.

Create your first workspace

  1. Sign in at yolo.studio .
  2. Click New Workspace on the dashboard.
  3. Name the workspace.
  4. Choose where the workspace’s repository comes from. A repository is required — every workspace (and every lane spawned from it) works from a checkout of it:
    • GitHub — pick an Existing Repo to clone, or create a New Repo.
    • Internal — host the repository inside YOLO with YOLO Internal Git: create a fresh private-by-default repo (with an explicitly confirmed public option), or pick one of your existing internal repos from the list.
  5. Click Create. Your container provisions and the workspace opens.

Have a project on your machine already? Run curl -fsSL https://yolostart.sh | sh from its folder and yolostart turns it into a workspace, after you approve what uploads.

Connecting a repository

You connect a repository when you create the workspace. YOLO Studio supports repositories from GitHub and from YOLO Internal Git — see Sign-in & Git Providers for how each one works.

When you connect a repo, YOLO Studio:

  1. Clones it into the sandbox under the workspace’s working directory
  2. Configures git credentials so commits and pushes work out of the box
  3. Makes the GitHub CLI (gh) available for opening PRs and managing issues (GitHub repositories)
  4. Makes your Internal Git credential available too (once you have one), so you can clone your internal repos from any workspace

Agents and terminal sessions inherit this setup — git commit, git push, and gh pr create work without additional setup.

What’s in a workspace

Out of the box you get:

  • An Ubuntu container running as the yolo user (UID 1000), with Node.js, Python, Git, SSH, the built-in coding agents OpenCode via YOLO, Claude Code, Codex, and Gemini CLI baked in (plus YOLO’s own CLIs; see CLIs). The remaining built-ins (Muse Code, GitHub Copilot, Kiro) and the community agents (Aider, Goose, OpenCode, Qwen Code, Neovate, Groq Code) install automatically the first time you pick them. Some need you to add a credential first. See Containers for the full list and the language-specialized sandbox flavors.
  • A tiled UI — open terminals, agents, preview tiles, watch tiles, and Kanban boards side by side. See Tiles.
  • A Workspace server — agents can inspect state, create new tiles, publish , and coordinate with each other through the same workspace you see. See Workspace MCP Server.
  • Kanban-driven agent work — put cards in the Ready column of the board connected to the Background Runner and it dispatches them into isolated agent , each an independent git clone with its own agent. Loops iterate an agent toward exit checks you define.

Where to go next

Last updated on
IntroductionSign-in & Git Providers