Changelog

Product updates

Keep up with our latest product updates and improvements.

Changelog

Product updates

Keep up with our latest product updates and improvements.

[OXVO Insights] AI tool connections with MCP

OXVO Insights
MCP
AI tools
analytics
developer
Glass analytics panel linked by one connector to a small assistant chip, with a key token symbolizing approved access

You can now connect AI tools such as Claude, ChatGPT, Cursor, and VS Code to OXVO Insights and ask questions about your analytics in plain language — for example, “How many visitors did we have each day last week?”

What changed

  • Connect an AI tool to one application and environment with read-only analytics access, using the Model Context Protocol (MCP).

  • Approve every connection in Console with OAuth sign-in. There are no tokens to copy or paste into a chat.

  • The connection exposes four read-only actions: list analytics definitions, run a query, retrieve a query result, and cancel a query.

Control and expiry

  • You have 10 minutes to approve a connection request once sign-in starts.

  • An approved connection lasts 30 days and renews in the background during that period; after 30 days you connect and approve again.

  • Review or revoke connections under App settings → General → Developer access → AI tool connections. Workspace administrators can see and revoke every connection in the workspace.

  • Connections cannot change data, settings, feature flags, or experiments, and they have no access to session replays.

Why it matters

Teams can investigate analytics inside the AI tools they already use, while access stays scoped to a single app, explicitly approved, and revocable — a safer pattern than sharing exports or credentials.

Availability

AI tool connections may not be turned on for every installation. If you do not see AI tool connections in App settings, ask your administrator.

OXVO

[OXVO Sessions] Vuex and Pinia state context for replays

Sessions
SDK
Vuex
Pinia
Privacy
A replay timeline connected to filtered application state changes.

The @oxvo/browser-vuex connector adds application-state context from both Vuex and Pinia to OXVO Sessions replay.

Capture controls

  • Record Vuex mutations or Pinia actions alongside the related state snapshot.

  • Use filter to exclude noisy updates.

  • Use transformer and mutationTransformer to reshape state and action payloads before capture.

State context can make UI behavior easier to diagnose, but the default transformers preserve the values supplied by the store. Production integrations should explicitly whitelist fields, exclude tokens, passwords, payment data, free-form values, and large collections, then verify one expected state or action entry in replay.

OXVO

[OXVO Builder] Workspace Library for reusable prompts and media

OXVO Builder
Library
Prompts
Theme Prompts
Media
A resource tray contains a reusable prompt card and a media tile.

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.

OXVO

[Access Control] Custom roles across Console, Builder, and Sessions

Console
Custom roles
Permissions
Builder
Sessions
A shared custom role connecting Console, Builder, and Sessions permissions.

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.

OXVO