Atlas is our centralized conversational UI. Embedded AI is broadly about applying AI to in-app experiences and individual Anvil2 components. An experience may use one or both approaches depending on what is appropriate.Within the app, use embedded AI patterns. Within the conversational interface, or with actions that immediately lead to it, use the Atlas Framework.
Anvil components are steadily gaining integrated AI labeling. When embedded AI elements are enabled, components receive a combination of visual and behavioral updates. See AI Mark for more.
Make users aware when an interaction involves AI. The AI Mark alone is sufficient disclosure in most cases, but complex workflows can need additional disclosure.
The mark itself denotes AI. Skip additional tooltips or popovers explaining that AI touched an element when the accompanying AI Mark is already present.Use the AI Mark when AI generates new content that wasn’t there before, or makes connections without the user necessarily being aware. Skip the mark on individual pieces of UI when the user is already aware that AI is crafting the data through the workflow that preceded the page they’re on.
When a label is available, use it to denote that the data below is AI-provided.When a label isn’t possible in the design, place the AI Mark next to the data itself.
The AI Mark alone communicates that something was touched by AI. Tooltips on the mark should explain how that data was deduced—for example, noting that an equipment brand was deduced from the model number.
Keep the AI Mark in place as long as the content remains untouched and AI-generated. Remove the mark the moment a user edits the content—edited content no longer reflects AI-generated output.
We recommend a max of five per page. Favor marking the places where AI meaningfully changes the outcome, and avoid treating the mark as decoration—this means you should end up with fewer marks overall. If many items in a section are related to AI in some capacity, consider putting the mark on the section header instead. When multiple marks crowd the screen, reduce marks before shrinking copy or layout. Keep mark density tied to real AI involvement, not page real estate.
Last modified on August 13, 2026
Was this page helpful?
⌘I
Assistant
Responses are generated using AI and may contain mistakes.
