---
title: "Website imports, guided setup, and clearer AI changes"
description: "A roundup of website style imports, guided brand setup, more reliable CSS imports, previewed AI changes, and clearer plan limits."
label: "Website imports, setup, and AI changes"
date: "2026-10-10"
---

This roundup covers the app improvements merged to main since our September
update.

### Import styles from your website

Website scanning is now available directly in the style import form, including
during onboarding and on every plan. Enter a URL, review the detected styles
alongside a screenshot, and choose which categories to import.

The report shows declared tokens and marks values measured from the page for
review. When the site switches between default and dark themes, you can inspect
both screenshots and their detected values. Colors retain transparency, and
missing values stay empty instead of being filled by convention.

Scanning currently targets the supported shadcn token vocabulary. Other custom
variables are reported as unmapped.

[Import styles](/docs/styles/importing-styles).

### Set up a brand in three steps

New brands open with a compact setup card: explore interactive rule examples,
import your styles, and connect an AI tool. Each step can be skipped, and imports
and connection guides open within the card.

Starter rules have a searchable pack browser and a preview of what they will add.
Setup recognizes rules and styles already saved to the brand, including work
completed on another device. An organization's first brand also gets a Default
project to help you connect.

The shadcn starter guidance has been rewritten into a smaller, more focused
collection for new brands. Existing brands keep their saved rules.

### Bring more CSS through the import

CSS imports now follow variable chains within the pasted stylesheet, including
Tailwind aliases and theme-specific values. Dark-theme variables resolve in their
own context, and supported calculations use the values from the paste.

Declarations inside `@layer` blocks are recognized. A value that a token cannot
hold is skipped with an explanation instead of failing the whole import. Reports
also explain when an expression was resolved into a single value or a reference
could not be followed.

Styles now identify whether imported values came from pasted CSS, a website scan,
or Figma.

### Keep AI changes tied to their preview

Connected AI tools now receive a preview before replacing existing tokens or
rules. Applying the change requires a confirmation code tied to that preview. If
the proposed changes or the values they would replace have changed, the tool must
get a new preview.

Website imports into projects also list the individual changes they would make.
This keeps the applied change aligned with the preview; approval prompts still
depend on the connected AI tool.

### Save the choices you make in the Agent

Choosing a different primary color after a website scan now carries that choice
into the saved draft. The scan no longer overwrites it during approval.

Draft comparisons use current values. Project imports save together through the
same importer used elsewhere, and retries no longer repeat an approved write.
Results also report failed changes more accurately instead of showing them as
applied.

[Meet the Agent](/features/agent).

### Give connected tools more room for rules

Rule responses repeat less metadata and use shorter labels. In measured Button
and Accessibility requests, removing repeated metadata reduced token usage by
about 25%.

Large responses now stay within their size limits, including for non-Latin text.
When a compliance request is too broad to repeat the required rules, the report
asks the tool to narrow its scope and clearly states that those rules were not
repeated for a final check.

### Connect with fewer detours

The Figma plugin opens its browser approval page automatically, with the pairing
code visible on both sides.

Connection guides open on Everywhere by default and include a Custom MCP option.
Figma Make and v0 guides use browser sign-in, and each guide finishes with a
connection check.

[Connect an AI tool](/docs/connect/overview).

### See what happens after a plan change

When a trial ends, a subscription lapses, or a plan is downgraded, brands and
projects beyond the plan's limits are retained and remain readable in the app.
Notices explain which ones are restricted; editing and connected-tool access are
blocked until they are covered again.

Owners can also see which members no longer have a seat. Upgrading restores access
within the new plan's limits.