Differences between code and your design system

The Differences tab of the design system lists every place where your code has drifted from it. A row can be a component that differs from the design, a value written past a token, an inline copy of a library asset, or a home-made twin of a system component. Each row says what was found, why it matters and who takes the next step: FISYCO or you.

Before you start

The design system in code is set up for the project. See Connect the design system.
Anyone in the project can read the list. Fixing, dismissing and bringing rows back is for project maintainers and workspace admins or owners.

Open Differences

Open the project and find Design system in code under From code.
Go to the Differences tab.

The list is sorted by severity and reach, so breaking changes in widely used places come first.

Above the tabs, How FISYCO handles differences shows each kind with its autonomy level: Design, Tokens, Icons and illustrations and Twins. Each level comes with one sentence on what it means, and twins are always not automatic. There are no switches on this screen: Change in settings leads to them. See Patches and autonomy.

Tabs: who moves next

The tabs split rows by who takes the next step, not by task status. Waiting for you opens by default, because only there a person is needed.

Tab	What is in it
Waiting for you	Differences FISYCO won't fix by itself: twins, and kinds set to Suggests or Off
FISYCO is on it	Queued for the next pass, an edit in progress, or a pull request open
Done	Fixed differences, and what FISYCO declined, with the reason
Dismissed	Rows people set aside, with the reason and who did it

An empty tab says what that means. Nothing is waiting for you tells you the rest is handled by FISYCO or already done.

Read a row

Column	What it shows
Found	The kind: Twin, Design, Token bypass or Asset copy
Where	The component name, the difference in words, and the places in code
Why it matters	Usages as a number and a bar relative to the most used row on screen, and the severity: breaking, additive or cosmetic
Who moves next	What happens to the row now, and why it waits if it does

Click a row with a component to open that component and its comparison with the design. See Compare components with the design.

Rows without a component, such as a token bypass, don't open. Their places open in a popover from the row instead. A place is a file and a line, linked to the repository at the last indexed commit.

Act on a row

Each row has one main action as a button. The row menu holds the rest: Open in repository and the dismiss reasons.

Fix now

Fix now appears on rows FISYCO knows how to fix but leaves to you, because their kind is set to Suggests or Off. Your request covers this one row. The level of the kind doesn't change.

Click Fix now.
The row moves to FISYCO is on it as Preparing an edit, started by you.
FISYCO proves the edit, then opens a pull request. The row shows Pull request #N open while it waits for review.

The proof and the daily pull request budget are the same as for automatic work. If the edit doesn't start, for example because today's budget is spent, the row returns to Waiting for you with that note. If FISYCO can't prove the edit, it opens nothing, and the row moves to Done with the reason.

Hand to an agent

FISYCO never fixes a twin: replacing it with the system component changes its API. A design edit FISYCO tried and declined is the other case. These rows offer Hand to an agent.

The dialog shows the whole task before you copy it. For a twin, it lists the places and asks the agent to find a fitting system component through the FISYCO MCP server, replace the twin and check the result. If nothing fits, the agent is told to stop and describe what is missing instead of writing another copy. For a declined edit, the task carries the reason and what differs from the design.

Click Copy the task and give it to Claude Code, Cursor or Copilot. The row stays in the list until the next index shows the difference is gone. For the agent to see your components and rules, connect it first: AI agents and MCP.

Dismiss with a reason

Open the row menu and pick a reason under Dismiss because:

It is an intentional copy
Not worth fixing
It is not a difference
We will fix it ourselves later

The row moves to Dismissed at once, and the message that confirms it offers Undo. In that tab, each row shows the reason and who dismissed it. Dismissed rows don't come back after re-indexing. Bring back returns a row to the queue.

You can't dismiss an edit in progress, an open pull request or a fixed difference.

What happens next

A row shows Fixed under Done once the difference is gone from the code, whether a FISYCO pull request was merged or someone fixed it another way.
Fix now, dismiss and bring back are recorded in the Activity log.
FISYCO changes your code only through pull requests your team reviews and merges.