Sessions SDK quick map

Use this section to implement browser capture, application-state visibility, and live assist workflows in one consistent rollout.

Choose your package set

Package	Purpose	Typical owner
@oxvo/browser	Core browser session capture SDK (replay, events, metadata, network, privacy controls)	Frontend platform / web team
@oxvo/browser-vuex	Vuex and Pinia state instrumentation plugin	Frontend feature teams
@oxvo/live-assist	Real-time assist plugin for co-browsing, remote control requests, and calls	Support engineering / operations

Rollout order that works in production

1. Install and validate @oxvo/browser in one environment.
2. Add privacy and network controls before broad traffic rollout.
3. Layer @oxvo/browser-vuex only for stores where state context is operationally useful.
4. Enable @oxvo/live-assist with consent messaging and role-based access rules.
5. Run a pre-release checklist for capture quality, permissions, and failure handling.

Read this section in sequence

• Install and capture your first browser session
• Install with a direct script tag
• Control lifecycle and runtime APIs
• Tune privacy, performance, and capture scope
• Track Vuex and Pinia state
• Enable live assist
• Run the production checklist and troubleshoot

Tip: Start with one staging project key and one production project key. Keep rollout controls independent per environment.

📷 Image (optional): Sessions SDK package architecture
Why: Helps teams align ownership and rollout order across capture, state instrumentation, and live assist capabilities.
File: docs/images/sdk-sessions-package-architecture.png
AI prompt: "Clean product documentation architecture diagram showing OXVO Sessions SDK stack with three layers: @oxvo/browser core capture, @oxvo/browser-vuex state plugin, and @oxvo/live-assist real-time support plugin, connected to OXVO Sessions backend and support workspace, modern SaaS UI style, neutral gray palette with one primary accent, crisp typography, no third-party logos, synthetic labels only, 1600x1000."