Skip to main content
Agent appearance is a presentation-only layer. It does not change knowledge, instructions, capabilities, tenant scope, or action permissions.

​
Appearance defaults

Owners can choose a theme, bounded accent token, avatar preset, header caption, header pattern, and Contact Button branding preference. Existing Agents start with Use current appearance, which preserves the previous App color and workspace branding behavior until an owner saves a different choice. The public Agent manifest exposes only bounded presentation values and safe hexadecimal color tokens. It never exposes uploads, internal database IDs, workspace policy records, or private owner data.

​
Assignment behavior

The Agent owns its default appearance. An Agent Chat App can continue to override its welcome message, suggested actions, and footer. When the Agent accent remains inherited, the App’s existing color is retained. Pages and Buttons remain the source of truth for installation and placement. The Agent builder displays those effective assignments and links to their editors instead of copying placement settings into the Agent.

​
Workspace-owned controls

Allowed domains, availability, offline visibility, language, conversation auto-close, and external protocol policy remain workspace settings. The Agent builder shows their effective values so an owner can understand delivery without creating conflicting records.

​
Accessibility

Theme presets use bounded design tokens. Public chat keeps keyboard focus indicators, mobile layout behavior, screen-reader labels, and reduced-motion handling. Contact Button does not add autoplay sound to Agent chat.

​
Compatibility and rollback

The appearance feature has an independent kill switch. When it is disabled, public chat uses the previous App colors, workspace header pattern, workspace branding, Agent initial, and description caption. Stored appearance settings are retained for later re-enablement.