Zoom Cobrowse SDK
Use this skill after the support workflow is clearly a browser co-browsing experience. If the user is still choosing between Zoom Contact Center, Virtual Agent, Video SDK, or Cobrowse, route through `start` or `plan-zoom-product` first.
Workflow
- Confirm the role model: customer page, agent console, session initiation, and how the PIN or link is handed off.
- Check auth and session setup before UI work: tokens, allowed origins, environment variables, and SDK loading.
- Design privacy controls early: masking rules, blocked elements, remote-assist permission boundaries, and audit requirements.
- Implement the minimal lifecycle first: initialize, start or join, subscribe to events, reconnect, and end.
- Add advanced capabilities only after the base session is stable: annotations, multi-tab persistence, custom PINs, and remote assist.
- When debugging, isolate browser support, CORS/CSP, token generation, third-party cookie behavior, and SDK event errors.
References
- Full preserved guide: [references/full-guide.md](references/full-guide.md)
- API reference: [references/api-reference.md](references/api-reference.md)
- Session lifecycle: [concepts/session-lifecycle.md](concepts/session-lifecycle.md)
- Privacy masking: [examples/privacy-masking.md](examples/privacy-masking.md)
- Remote assist: [examples/remote-assist.md](examples/remote-assist.md)
- Common issues: [troubleshooting/common-issues.md](troubleshooting/common-issues.md)