Workspaces

A workspace is your cloud development environment in YOLO Studio. It gives you one container-backed repo plus a tiled UI for terminals, agents, previews, and agent .

The vocabulary used throughout this section — , , , — is defined on the Concepts page.

Architecture

Container: Ubuntu-based running as the yolo user
Services: terminals (port 7782) and the Container API (port 7779). Port 3000 is left free for your own dev server.
Storage: Workspace files live in the container filesystem; lanes are created under /home/yolo/lanes/<name>
Networking: routing via k8s-gateway proxy
UI Model: live on . The default desktop is exposed as main through the API.

Workspace Lifecycle

Creating — Container image pulled and pod scheduled
Running — Workspace active and accepting connections
Paused — Pod torn down (manually or after the idle timeout); the workspace volume is kept so it can resume
Terminated — Pod and workspace volume deleted, resources freed

What Lives In A Workspace

A tile is a view of something running, never the thing itself. Closing a tile does not cancel the underlying work; it only detaches the view.

Terminal tiles for direct shell access
Agent tiles for autonomous coding sessions
Preview tiles for running web apps and navigating routes
Kanban tiles — views of a board whose cards the Background Runner dispatches into isolated git
-managed tiles and for agent-driven workspace automation

Where to go next

Tiles — layout, desktops, notes and tags, the Marketplace, and Quick Lanes
Tile Types — a page for every kind of tile: agents, terminals, previews, boards and more
Workspace MCP Server — agent-driven tile control
Orchestration — context warm-start, shared scratchpad, preview auto-setup, workspace layouts, watch tiles
Containers — runtime backing the workspace
Background Runner — dispatches Kanban cards into isolated agent lanes