The workspace-scoped Library in OXVO Builder brings reusable prompts, Theme Prompts, and media into one product surface.

What’s included

• All, Theme Prompts, Prompts, and Media views.

• Reusable implementation instructions with project-specific values kept as explicit variables.

• Visual-system guidance and generated or uploaded media that can be organized for use across Builder work.

Library helps teams reuse the right level of context without copying an entire project. Use a template instead when routes, components, and source need to move together. Keep credentials, customer data, private domains, and unreviewed media out of reusable Library items.

Workspace administrators can use custom roles in OXVO Console to combine support permissions with Builder and Sessions access in one job-specific role.

Access can be separated by job

• Distinguish Builder access from Builder administration.

• Scope Session Replay, Metrics, Data Management, Live Assist, and AI Live Assist capabilities.

• Keep Team and Inbox membership separate from what a role is allowed to do.

This reduces the need to grant the broad Administrator role just to unblock one product workflow. Exact permission names and custom-role support depend on the plan and enabled modules, so test both allowed and denied actions after assigning or changing a role.

Design Add-ons give Builder teams a focused way to strengthen one part of an existing app without turning the request into a full redesign.

What changed

• Browse reusable patterns for cards, hero systems, maps, shaders, and text treatments where those catalog categories are available.

• Add a pattern to the composer and target a selected component or clearly named section.

• Review responsive behavior, accessibility, performance, contrast, and reduced-motion behavior before publishing.

An add-on contributes implementation guidance; it does not silently modify the project. That keeps the visual change bounded and easier to review while preserving existing actions, data, routes, and important UI states.

We added Live Chat Loader to OXVO Messenger to reduce the performance impact of chat widgets on page load.

Read the full blog post: Live Chat Loader: keep live chat fast without the performance hit

What's new

• Lightweight launcher first: show a placeholder launcher immediately.

• Deferred full load: load the full Messenger SDK only when the page is idle or the user interacts.

• liveChatLoader is false by default.

Enable it

<OxvoMessengerProvider
  baseUrl="https://your-oxvo-domain"
  websiteToken="your-website-token"
  liveChatLoader={true}
/>

<OxvoMessengerProvider
  baseUrl="https://your-oxvo-domain"
  websiteToken="your-website-token"
  liveChatLoader={true}
/>

<OxvoMessengerProvider
  baseUrl="https://your-oxvo-domain"
  websiteToken="your-website-token"
  liveChatLoader={true}
/>

Configure appearance (optional)

<OxvoMessengerProvider
  baseUrl="https://your-oxvo-domain"
  websiteToken="your-website-token"
  settings={{
    position: 'left',
    theme: 'dark',
    widgetStyle: 'flat',
  }}
  liveChatLoader={{
    enabled: true,
    appearance: {
      position: 'right',
      horizontalSpacing: 24,
      verticalSpacing: 24,
      messengerColor: '#2d6bff',
      type: 'expanded_bubble',
      launcherTitle: 'Support',
    },
  }}
/>

<OxvoMessengerProvider
  baseUrl="https://your-oxvo-domain"
  websiteToken="your-website-token"
  settings={{
    position: 'left',
    theme: 'dark',
    widgetStyle: 'flat',
  }}
  liveChatLoader={{
    enabled: true,
    appearance: {
      position: 'right',
      horizontalSpacing: 24,
      verticalSpacing: 24,
      messengerColor: '#2d6bff',
      type: 'expanded_bubble',
      launcherTitle: 'Support',
    },
  }}
/>

<OxvoMessengerProvider
  baseUrl="https://your-oxvo-domain"
  websiteToken="your-website-token"
  settings={{
    position: 'left',
    theme: 'dark',
    widgetStyle: 'flat',
  }}
  liveChatLoader={{
    enabled: true,
    appearance: {
      position: 'right',
      horizontalSpacing: 24,
      verticalSpacing: 24,
      messengerColor: '#2d6bff',
      type: 'expanded_bubble',
      launcherTitle: 'Support',
    },
  }}
/>

Override precedence

1. defaults

2. settings passed to init

3. liveChatLoader.appearance (highest priority)

Note: widgetStyle is inherited from Messenger settings and can't be overridden via liveChatLoader.appearance.