Limits you can read, held by the code
Saving a design version through an assistant now needs its own permission, customer-space run requests expire after a week, and stop reaches a model call already under way. What changed, and what it means for tokens you already use.
Engineering buyers ask us the same question in different words: what is the AI allowed to do on its own? The platform page now answers it in six short limits, from "only adoption changes a design" to "your files stay in the EU". This week we made several of those limits tighter, and each one is held by the server, not by a setting an assistant can ignore.
Saving a version needs its own permission
An assistant you connect with a token can read your designs and prepare a change. Saving that change as the design's next version is now a separate permission, adopt. A token with write access can prepare and preview, but it cannot save.
Only a token you create yourself in the workspace can hold adopt, and you choose it there on its own line. A browser-approved connection never gets it. The reason is simple: an assistant that has just read text someone else wrote should not also be able to save a version, unless a person gave it that right on purpose.
If you used an assistant to adopt changes before this week, its token no longer does. Create a new token that asks for adopt, or adopt the change yourself in the workspace.
A request waits a week, then expires
When someone you invited to a customer space asks for a checks run, the request now waits seven days for the designer who owns the project. After that it shows as Expired without an answer. An approval that arrives too late changes nothing: no run starts and no credit is used.
Stop means the call stops
Cancelling a design or concept run used to stop it between steps, while a model call already under way ran on until it finished. Stop now reaches that call too. A cancelled run ends as cancelled, and its credit hold is released as before.
What the roles remember can be checked
The notes the AI roles keep about a project can now have an end date. After it, the note is no longer used. Every change to a note is kept in its history, with who made it, and a correction can be undone. If a note changed while you were reading it, your edit is refused and you see the current text. Passwords, API keys and private keys are removed from notes before they are saved, and again before they are read.
A monthly report of model use
The Usage panel has a monthly report: the model calls behind your design runs, the helper calls listed apart, and the credits used. A CSV gives one row per call. Where a provider did not report its token count, the report says "not reported" rather than 0. Company administrators can see the company's figures.
Scope
- The report counts tokens and credits. It does not show a price.
- Existing tokens were not widened. Adopting through an assistant needs a new token.
- The seven-day wait applies to checks runs asked for from a customer space.
- AI prepares proposals. Engineering approval and release stay with your engineer and the agreed authority.