Skip to Content

Tiles

Tiles are the building blocks of a YOLO Studio workspace. Each tile is a resizable panel — a terminal, an agent, a preview, a board — and each is a view: closing a tile never cancels the work behind it.

Tile types

Every kind of tile — agents, terminals, previews, boards, and the rest — has its own page under Tile Types, along with the controls every tile shares.

Layout

Tiles are arranged in a responsive grid. You can:

  • Add new tiles from the workspace toolbar’s tile picker.
  • Move a tile by dragging its header, and resize it by dragging the edges between tiles.
  • Split a tile left, right, up or down from its menu, so the new tile opens beside it.
  • Zen Mode fills the screen with one tile (double-click the header, or press Esc to leave).
  • Minimize a tile to keep it running out of the way.
  • Close tiles you no longer need.

With more than one desktop, Move to Desktop moves a tile to another desktop, and the pin icon keeps a live copy of a tile on your main desktop.

Multiple tiles can run simultaneously, letting you monitor several agents or keep a terminal open alongside an agent session.

Tile notes & tags

Every tile carries its own notes and tags, shown in the title bar.

  • Notes — choose Add note to jot free-form notes for a tile (what it’s for, what you asked an agent to do, where you left off), up to 4,000 characters. Notes save when you close the editor or press ⌘/Ctrl+Enter, and stay with the tile across refreshes and desktop switches.
  • Tags — add short labels from the title bar to group and mark tiles at a glance. Type a tag and press Enter (or comma) to add it — up to 12 tags of 32 characters each; tags appear as colored chips next to the tile name, and hovering a chip reveals an × to remove it.

Both are per-tile and persist on the workspace, so they survive closing and reopening a tile.

Marketplace

The Marketplace is a catalog of tile apps you can install into your workspaces. Reach it from:

  • Dashboard — Marketplace in the sidebar navigation opens the global catalog at /apps. An Install into workspace picker in its header lets you choose which workspace an install lands in. Each workspace card also has a Browse marketplace button that opens the catalog scoped to that workspace (/workspaces/[id]/apps).
  • Workspace — the Marketplace button in the workspace toolbar (or the toolbar’s overflow menu when space is tight) opens the catalog in a modal scoped to the current workspace, without navigating away.

Browsing and installing

The store lists curated apps with descriptions, screenshots, category tags, and changelogs. You can narrow the list by:

  • Text search — name, description, or publisher.
  • Filters — All, Installed, MCP Servers, and category chips.
  • Sort — A–Z or Popular.

Each app card shows a verification badge (YOLO Labs, verified or unverified) so you know who published it, and its price. Open an app to see its details and install it — you review what it asks for before granting anything (see App). Installed apps show Open app on their card and appear under the Installed filter, where each has a Manage menu (Details, Edit permissions, Revoke).

Your personal apps

Apps you built with yolo tileapp publish --personal appear in your own Marketplace catalog, labeled personal app — only you see them; they are never listed for other users. See Building Tile Apps → Personal apps for how to create one.

Quick Lane

The Quick Lane button in the workspace toolbar creates a throwaway agent tile in one click — no catalog, no config flow. It mints an isolated lane (quick-<ts>) and places your primary agent on it immediately, so you can jump straight into a quick edit without deciding where the work lands.

Your primary agent is the highest-priority entry from your workspace preference (which you set in workspace settings), falling back to your account preference, then to the lowest-order built-in agent.

Closing a Quick Lane

Closing a quick-lane agent tile — or any agent tile that owns its lane — triggers a lightweight “Keep your changes?” flow instead of silently discarding the lane. It’s skipped while another tile still uses the lane.

  • No work (no commits and no uncommitted edits) — the lane is silently deleted after the agent tears down and a final check confirms nothing was actually written.

  • Work present — a dialog shows the lane’s diff for review and offers five options:

    OptionWhat happens
    Merge into workspaceA standard three-way merge of the lane’s commits onto the workspace base. A merge commit is produced.
    Squash & mergeAll lane commits are squashed into a single commit, then merged into the workspace. Keeps history clean.
    Rebase & mergeThe lane’s commits are rebased onto the workspace base tip and fast-forwarded (linear history).
    DiscardAfter a confirmation, the tile closes and the lane and all its commits are thrown away.
    Close & keep laneThe tile closes, but the lane (and its commits) is left in place, untouched, for later.
  • Merge conflicts — the tile stays open, its agent is sent a conflict-resolution prompt via the context bus, and the dialog switches to Finish merge / Abort & keep lane controls. Once the conflicts are resolved and committed in the lane, click Finish merge to complete the integration (resolved changes land as a single squashed commit).

  • Rebase conflicts — the same flow for Rebase & merge: the agent is asked to resolve and git rebase --continue, and the dialog offers Finish rebase / Abort & keep lane. Reopening the dialog on a lane with a paused rebase or merge returns straight to these controls.

  • Other operation in progress (e.g. a cherry-pick) — the dialog can’t drive it, so it only offers Close (keep tile open); finish or abort the operation in the tile, then close the tile again.

Uncommitted edits are committed automatically before any of the integration options run, so last-moment changes are preserved.

Agent-Created Tiles

Agents can create visible tiles through the Workspace MCP Server — for example, studio.create_agent_tile and studio.create_preview. Because tile creation changes the user-visible workspace, these calls should be used intentionally rather than speculatively.

Last updated on