# Review a design change on live frames

Review a pull request's design change on live frames: base beside the change, by theme and device, with comments through your own gh.

> **In the pilot**
>
> The design system module is in the pilot. It is on for pilot orgs first. An org admin can tell you whether yours has it.

The review page shows a pull request's components the way people will see them: the default branch on one side, the pull request on the other, each story running live in a frame. You pick a theme and a device, pin a comment on the exact tile, and give your verdict.

Before you start:

- Your org needs the `design` module. When staff turn off the `design` kill switch, the review page is unavailable. See [kill switches and modules](/reference/kill-switches-and-modules).
- To open a review, you need a role on the design system and GitHub read access to the pull request's repo.
- To comment or give a verdict, you need to be an org admin, a member with any role on the system, or a guest who is a contributor or maintainer on it.
- Frames need a Storybook or preview on a host your admin approved. See [Approve the hosts frames come from](#approve-the-hosts-frames-come-from).

> **Desktop app only**
>
> Posting comments and verdicts to GitHub, opening a story in the pane, and Ask EasyCode run in the desktop app. On the web, comments and verdicts stay in EasyCode.

## Open a pull request's review

Open the design system and go to **Open changes**. See [open changes across repos](/design-system/open-changes).

Find the pull request's lane and press **Review**. The header shows the pull request, its branch and its checks; **Review on GitHub** opens it on GitHub.

The left side is "Latest (default branch)"; the right side is "Pull request" at its head. Token changes are on the Open changes page, not here.

## Filter by component, theme and device

Use the filters above the surface:

- **Component**: all changed components, or one.
- **Theme**: every theme the system defines, or one.
- **Device**: one device at a time, from the product's devices and the standard catalogue, or **Bare** for no device frame.

The surface pans and zooms. Up to 16 frames nearest the centre of your view run live; the rest show as cards until you move to them. At phone width you see one side at a time: switch between **Base** and **Pull request**. More than 20 changed components are paged with **Previous** and **Next**.

## Pin a comment

Press **Comment**.

Click the name in a tile's header. The comment box names the anchor: component, state, theme, device and side.

Write your comment and press **Send**.

The tile gets a numbered pin, and the thread appears under **Threads** with the same number. Press a pin to jump to its thread, where people reply and resolve it.

## Post comments and verdicts to GitHub

A comment starts in EasyCode and reads "Not on GitHub". In the desktop app, its author presses **Post to GitHub**, and EasyCode posts it with your own `gh` login, so it appears on the pull request as yours. Comments written on the web stay in EasyCode until you post them from the desktop app.

To give a verdict, add an optional note and press **Approve** or **Request changes**. In the desktop app the verdict is posted as your GitHub review, on the head you looked at. On the web it is recorded in EasyCode only and reads "In EasyCode only: not a GitHub review".

## Ask EasyCode to apply the comments

Any full member who can review the pull request can hand its open threads to a session.

In the desktop app, press **Ask EasyCode**. It shows when you are a full member, the pull request is open and comes from a branch in the same repo, and Claude or Codex is ready on your machine.

Tick the threads to apply (up to 20 open threads). The dialog also says what CI reported for the branch.

Press **Ask EasyCode**. A session opens on the pull request's branch, isolated, with those threads.

The agent commits but never pushes. Review its work, then push from the session's git panel.

Each thread the agent addressed reads "Committed, not pushed yet", then "Answered in" with the commit's short sha once the commit is on the pull request. The tiles reload at the new head.

EasyCode says why when it can't help, for example a pull request from a fork or a repo you can't push to. If you have no clone, the dialog offers one. Applying comments needs git 2.54 or later.

## Approve the hosts frames come from

Frames load only from hosts on the org's approved list.

As an org admin, open **Settings → Design**.

Under **Approved hosts**, add one origin per line, such as `https://storybook.northwind.example`.

Press **Save**.

Members can read the list but not change it. When a side's host is not approved, admins see "This host is not on the approved list" with a link to the settings; everyone else sees "Ask an admin to approve this host".

## What falls back to a card

A tile shows a live frame when its host is approved and the story renders. Otherwise it steps down:

- In the desktop app's browser, a tile that can't run live offers **Open in pane**, which opens the story in the session's browser pane.
- Everywhere else it becomes a card with the component, its state and an **Open story** link.

A story that errors or does not render in time also falls back. Press **Retry** in its header to try again. After a merge or close, the page says the preview is gone and live frames stop.

## Related

- [Open changes across repos](/design-system/open-changes)
- [Studio share and review](/guides/studio-share-and-review)
- [Roles and access](/overview/roles-and-access)
