zoom-cobrowse-sdk

Enable real-time co-browsing with annotations and privacy masking across web, mobile, and desktop.

65|12|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/zoom/skills --skill zoom-cobrowse-sdk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zoom-cobrowse-sdk
Source: https://github.com/zoom/skills/tree/main/cobrowse-sdk
Command: npx skills add https://github.com/zoom/skills --skill zoom-cobrowse-sdk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Cobrowse SDK enables real-time co-browsing between customers and agents with built-in privacy masking and annotation tools to improve support efficiency.

Core Features & Use Cases

  • Real-time co-browsing of customer pages across web, mobile, and desktop contexts.
  • Annotation tools, privacy masking, remote assist, and multi-tab session persistence to enable seamless collaboration.
  • BYOP options and JWT-based authentication to integrate with existing ticketing or support workflows.

Quick Start

Get credentials from Zoom, set up a server for JWT generation, initialize the customer SDK with the token, and start a session to receive the PIN.

Frequently Asked Questions about zoom-cobrowse-sdk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up real-time co-browsing for customer support agents?

Real-time co-browsing requires obtaining credentials from Zoom, configuring a server for JWT generation, initializing the customer SDK with the token, and starting a session to receive a PIN for agent-customer collaboration.

What is co-browse technology and how does it handle customer privacy?

Co-browse technology enables live agent viewing and annotation of customer pages across web, mobile, and desktop contexts, featuring built-in privacy masking to redact sensitive data during remote assistance sessions.

Can I integrate co-browse with my existing ticketing system using JWT authentication?

Yes, co-browse supports BYOP options and JWT-based authentication to integrate with existing ticketing or support workflows, utilizing server-side JWT signing for validating sessions.

Does the co-browse SDK work across web, mobile, and desktop platforms?

Yes, the co-browse SDK supports real-time co-browsing of customer pages across web, mobile, and desktop contexts, distributed via CDN or npm for flexible integration.

What are the limitations of using JWT authentication for co-browse sessions?

JWT authentication for co-browse requires server-side signing infrastructure and valid Zoom credentials, meaning you must maintain a backend service to generate tokens for initializing customer SDK sessions.

Why do I need server-side JWT signing to enable remote assistance?

Server-side JWT signing is required to securely authenticate and initialize the customer SDK, ensuring that only authorized agents and customers can establish co-browsing and remote assistance sessions.