Setting the file. One moment. RUNBOOK · Zoom Cobrowse SDK · anthropics/knowledge-work-plugins · Skills Docs
Use this before deep debugging. It catches the most common Cobrowse failures quickly.
22
Validate Data
Tech Debt
62
Recruiting Pipeline
71
Vendor Check
125
Zoom Meeting SDK Web
88
Vendor Review
181
Create An Asset
Video Sdk/web
- Agent-skill standard entrypoint is
SKILL.md.
- This runbook is an operational convention (recommended), not a required skill file.
SKILL.md is also a navigation convention for larger skill docs.
- Customer role (
role_type=1) starts session.
- Agent role (
role_type=2) joins session.
If your demo only has one generic role, expect broken join behavior.
- Use customer SDK event
pincode_updated as the only user-facing PIN.
- Agent must join with that same PIN.
- Do not show provisional/debug PIN values from backend records.
Common symptom if wrong: Pincode is not found / error 30308.
- Sign JWT on backend only.
- Include required claim names exactly (for example
user_id, not custom aliases).
- Use SDK Key for SDK token context; keep SDK Secret server-side.
If claim names are wrong, token is rejected before session logic.
- Customer gets customer JWT and starts session.
- PIN is generated on customer side (
pincode_updated).
- Agent gets agent JWT and joins with that PIN.
Starting agent flow before customer session is active often causes join failures.
- CDN path: customer SDK + Zoom-hosted agent desk iframe.
- npm path: custom integration (BYOP mode required for custom PIN control).
If using npm agent integration without BYOP expectations, flow mismatches happen.
- HTTPS required (except loopback/local dev).
- CSP/CORS must allow Zoom domains.
- Third-party cookie/privacy settings can affect reconnect behavior.
Do not treat extension/adblock warnings as root cause until API/session checks fail.
- Backend config endpoint returns expected credential flags.
- Customer page shows a single Support PIN from SDK event.
- Agent page join uses same Support PIN and returns actionable response (not generic 404).
Expected: customer/agent pages load and config endpoint returns valid JSON flags.
- Invalid token -> check JWT claim names and signing secret.
- Agent cannot find PIN -> wrong PIN source or wrong session order.
- Session drops on refresh -> check reconnection window and browser privacy/cookies.
- Works locally, fails prod -> check HTTPS, CSP/CORS, reverse proxy pathing.
RUNBOOK.md