---
title: "Easier connections, clearer imports, and token delivery checks"
description: "A roundup of improvements to tool connections, Figma imports, rules, token exports, project history, and account settings."
label: "Connections, imports, and token delivery"
date: "2026-09-25"
---

This roundup covers the app improvements merged since our August update,
through September 23.

### Connect tools with less setup

Supported tools can now connect through browser sign-in without asking you to
copy an API key. The Connect dialog includes installation links for Cursor
and VS Code, a prefilled Claude connector form, and updated instructions for
Claude Code, Codex, Figma Make, v0, and Lovable. Creating a project opens
Connect so you can choose a tool straight away.

The approval screen names the app requesting access and lets you choose the
project. It uses your own project key, creating one with the project's default
permissions when needed. Manual API-key connections remain available, with
clearer permission details and key naming.

CLI setup now produces configurations without embedded keys by default.
Connection guides finish with a check in your AI tool, and more connection
errors explain what to do next.

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

### Bring Figma variables into a brand

The Figma plugin supports browser approval using a short device code. Choose
your brand, select variable collections, and preview changes before applying
them. Improvements to the first-run collection picker, variable mappings,
and connection status make it easier to see what is connected. You can also
copy variable data as JSON.

[Use the Figma plugin](/docs/connect/figma-plugin).

### See what an import will change

Token import reports distinguish matched tokens from changed values, with
clearer reporting of unchanged and unsupported values. Reports use consistent
fields across the app, plugin, Agent, and connected tools.

Project imports leave matching brand values inherited instead of creating
unnecessary overrides. Brand imports explain when changes affect projects
that inherit those values.

You can also paste a shadcn `components.json` file to record its configuration,
including style, base color, icon library, and RTL settings. Theme values,
fonts, and radius stay as they are because that file does not contain them.

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

### Get compiled tokens for your stack

Connected tools can request ready-to-use token exports for CSS, Tailwind v4,
and Tailwind v3. Tailwind v4 delivery includes the theme mapping; Tailwind v3
provides the stylesheet and configuration together. Exports respect a
project's pinned version.

Stylesheet verification compares a supplied stylesheet with the canonical
export. After a clean Tailwind v4 check, the compliance report also directs
the AI tool to run the project's token-usage linter, or ask before setting one
up. The stylesheet check itself does not inspect how every component uses
tokens.

Standalone ruleset exports and CLI token exports give you more ways to take
your design system into a project.

### Organize guidance and see who changed it

Rules and named rule groups have a more consistent editor across library and
style pages. Rule details show their creator, last editor, and last change,
with clearer context for project overrides. A project can hide a group and
its child rules together.

Starter packs have previews so you can read their guidance before applying
it. Connected tools have better access to Content guidance for copywriting,
and output limits preserve required rules. Saved AI instructions warn when
they are out of date.

[Organize rules](/docs/rules/organizing).

### Give icons and logos their own guidance

The dedicated Iconography page brings icon-library selection, installation
and import snippets, and usage rules together. Brand assets support logo
usage rules, and wide wordmarks retain their proportions where they are
displayed.

[Manage iconography](/docs/library/iconography) and
[brand assets](/docs/library/brand-assets).

### Understand what each project receives

Project overviews make inherited guidance and project overrides easier to
review. Delivery status and version-history indicators show which saved
version is being delivered. Brand and project overview improvements bring
setup health, project details, and connected work into view.

Project notes are stored by source so one codebase's notes do not overwrite
another's. Activity now identifies changes made by the Agent separately from
changes made by people.

[Review project overrides](/docs/projects/overrides) and
[version history](/docs/workspace/version-history).

### More control over your workspace and account

Appearance settings include UI Rules, brand, and custom themes, plus light,
dark, and system modes and sidebar preferences. Organization trash provides
a place to manage deleted brands. Error screens offer clearer routes to
feedback and support.

Trial reminder emails arrive three days before a trial ends. Other account
improvements include plan-limit and connection reminders, more reliable
sign-out and membership handling, marketing preference synchronization, and
analytics cookie controls.