Orchestration

YOLO Studio workspaces go beyond isolated terminals. Tiles can share context, react to each other’s results, and help several agents work together across separate git lanes.

This page is the operator-level view of those features.

Context injection (warm-start)

Every agent starts with context about the workspace. On spawn, the system generates a context file by merging:

• Role template — architect, implementer, reviewer, etc.
• Recent git diffs — what’s changed in the repo
• Message bus history — what other agents have been doing
• Shared plan — the team’s .yolo/shared/plan.md in the workspace (see below)

Agents hit the ground running instead of starting from a blank slate.

Shared scratchpad

Multiple agents in the same workspace coordinate through a shared plan at .yolo/shared/plan.md, relative to the workspace root (not your home directory). When the file exists, its contents are automatically injected into every agent’s context.

One agent outlines the approach, another implements the backend, a third handles the frontend — and they all stay aligned through a shared, living document. No manual relay required.

Preview auto-setup

Adding a preview tile can auto-detect a runnable app, start the right command, and persist that setup to .yolo/preview.json so later sessions can restart it consistently. Persistence is automatic — there is no save prompt: a running preview with a known command is saved silently if it isn’t in .yolo/preview.json yet. A preview adopted without a command isn’t persisted until an agent registers it. See Preview Tiles.

Workspace layouts

Save the current desktop as a reusable layout. It captures tile types, names and sizes, agent roles and models, dependency wiring, feedback loops, and watch patterns — then reapply it to any workspace from the Layouts menu.

Layouts are trimmed for portability: only the tile configuration is kept (session-specific state is left out), and absolute paths are stripped from watch commands. Best-workflow patterns become reusable templates instead of tribal knowledge.

Save a layout: click “Save as layout” in the workspace toolbar. Give it a name and it’s available in the Layouts menu for all future workspaces. Applying a layout to a desktop that already has tiles asks whether to add the layout’s tiles alongside them or replace the desktop.

Watch mode tiles

A first-class tile type that runs a command whenever specified files change. Configure a glob pattern and a command, and the watch tile handles debouncing, execution, and streaming output with color-coded pass/fail results.

Pattern:   src/**/*.ts
Command:   npm test
Debounce:  2000ms

Watch tiles integrate with the full orchestration system — they can publish artifacts on each run, feed into dependency triggers, and pair with agent tiles for automated fix loops.