AI Requests

Not every tweak is a scrub of padding. When something needs real logic, leave the AI a message: pin a free-text request to an element, a region, or the whole page in Layout Live, and carry on. Your agent picks the request up over MCP, does the work in your actual source, and reports back. The pin on the page recolours as the status changes, so you can see at a glance what is waiting, what is being worked on, and what is finished.

The full loop

Pin a request. Select an element (or drag out a region, or target the whole page), open Ask AI from the floating selection toolbar, and type what you want changed. The request is written to .layout/live/ with its exact source location and appears in the Requests tab of the Layers panel.
The agent picks it up. In Claude Code (or any MCP-capable agent), the get-pending-requests tool returns the queue, each request with the file and line it is anchored to, so the agent knows exactly what “this button” means.
The agent reports progress. The mark-request tool sets the request to in progress when work starts and done when it finishes, with an optional note describing what was changed.
You see the result. Pins recolour on the page as statuses change, and completed entries show “Resolved by agent”alongside the agent's note. Your dev server has already hot-reloaded the change, so the fix is on screen.

Status	Pin colour	Meaning
Pending	Amber pin	You pinned the request and no agent has picked it up yet. It is waiting in the queue.
In progress	Blue pin	An agent called mark-request with status in-progress. Work has started on it.
Done	Green pin	The agent called mark-request with status done. The entry shows 'Resolved by agent' plus any note the agent left.

The compliance meter's Ask AI button files a prefilled request describing a specific violation, so routing an off-system value to your agent is one click. See the compliance quick-fix section on the Live overview.

Screenshots

Every pinned request automatically captures a screenshot of the page at the moment you filed it. Region requests are cropped to the pinned region, so the image shows exactly the area you were talking about. Agents fetch the stored image with the get-live-screenshot MCP tool by passing the request id, or omit the id for a fresh capture of whatever Live is showing right now.

This closes the biggest gap in text-only requests: the agent sees what you saw. “This looks cramped” stops being ambiguous when the request arrives with a picture of the cramped thing.

Team webhooks

Requests can post to a team channel as they are filed. In Live's Settings, add a webhook endpoint and choose the format:

Slack: an incoming-webhook URL; requests arrive as formatted Slack messages.
Discord: a channel webhook URL; same idea, Discord-formatted.
Generic: any HTTPS endpoint; Live sends a JSON payload with the request text, target, status, and project, for your own tooling.

This is useful even without the shared cloud queue: a designer pinning requests on a review build can feed a #design-fixes channel that the whole team sees.

Team sync: the shared queue

Requests can also sync to your organisation's shared cloud queue, so the whole team works from one list rather than per-machine logs. Setup takes two steps:

Create an organisation API key in the Studio dashboard under Settings → API Keys.
Paste the key into Live's Settingsand enable team sync. From then on, requests you pin are pushed to the org queue, and teammates' requests flow back to you.

Once syncing, two new surfaces appear:

The Team section in Live.Teammates' requests for the current project show up in the Requests tab with an Adopt button. Adopting a request brings it into your local queue so your agent can pick it up and resolve it, even though someone else filed it.
The Live Requests page in the Studio dashboard. The whole team's queue in one place, grouped by project, with status filters (pending, in progress, done). Useful for leads triaging what is outstanding without opening Live at all. See Dashboard & Settings.

Requests work fully offline without team sync: they live in .layout/live/ and agents read them from disk even when Live is closed. Webhooks and team sync are additive layers on top.

Next steps

The Design Tab , edit tokens, browse components, and read guidelines inside Live.
CLI & MCP Server , the full reference for get-pending-requests, mark-request, and get-live-screenshot.