0.9.0-beta.14Beta

Changed

• An AI agent can take back any of its changes, even ones it didn't name. Every change an agent makes now gets an id, and Polyform tells the agent what it is. An agent can also take a change back by its name, such as "Recolour buttons". Before, an agent that gave its changes no id could only take back its newest one. When two changes share a name, Polyform asks the agent which one it means.
• When an agent recolours layers that use a shared style, Polyform tells it that the layers no longer follow the style, and that changing the style would have recoloured them all and kept them linked. The agent guide also asks agents to check this before they repaint.
• After an agent resets an instance's overrides, Polyform tells it what each property now says, such as the label going back from "Go" to "Buy", so the agent doesn't have to guess.
• An agent can name a page and a layer on it together when it looks for layers. That used to be refused even when the layer was on that page.
• The Claude Code skill is version 1.16.0, with all of the above and the reading limits below. The Agent connection window offers Update.

Fixed

• An AI agent's first look at a big document no longer fails (F-321). On a page with a few hundred layers, the summary an agent reads first was larger than Claude Code accepts in one reply, so the agent got a file instead and spent several more steps getting round it. The summary now stays under 32 KB. It always includes the page and layer counts. As many layers as fit come next, top-level layers first, and the summary says what it left out and how to read the rest.
• A document with a big design system no longer makes an agent's first look fail either (F-323). The summary listed every component, style and variable in full, so about 300 components, or 1,000 styles or variables, took it over the limit again; an imported design system gets there quickly, because every variant is a component. The layers and these lists now share the 32 KB. When they don't all fit, each list keeps the ones the document uses most, says how many there are in all, and tells the agent how to read the rest: the agent can ask for one list on its own, page by page, or search for components by name. A component set with hundreds of variants names its first 100.
• Reading a big selection no longer goes over the limit (F-323). With 200 cards of 20 layers selected, the reply to an agent was 268 KB. It now stays under 32 KB: the selected layers come first and their contents as far as room allows, and an agent can page through a selection of any size.