[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFDYK496J8RT1PJHWBPWWF":3,"skill-same:01M6MFDYK496J8RT1PJHWBPWWF":95},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":65,"commitSha":66,"skillDirectory":67,"forksCount":68,"repositoryHtmlUrl":69,"repositoryHomepageUrl":70,"ownerHtmlUrl":71,"ownerBlogUrl":72,"ownerDescription":73,"updatedAt":74,"install":75,"resources":88},"01M6MFDYK496J8RT1PJHWBPWWF","cometchat-js-v5-sdk",null,"Add voice & video calling to any web app FROM SCRATCH with the headless CometChat Calls SDK v5 (`@cometchat\u002Fcalls-sdk-javascript@5`) — no prebuilt UI Kit. init→login→generateToken→joinSession, event listeners, in-call actions (mute\u002Fvideo\u002Fscreen-share\u002Frecord\u002Flayout), meet-style session rooms AND 1:1 ringing (Chat SDK signaling + Calls SDK media). Triggers: 'add calling from scratch', 'standalone video call', 'headless calls sdk', 'build my own call UI', 'meeting room join by session id', 'one-on-one ringing call without uikit'.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-js-v5-sdk\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"sdk","js","cometchat js v5 sdk","cometchat","framework-agnostic","scratch","for","vue","ui","recipes","screen","login","layout","next","browser","react","angular","webrtc","safari","join","kit","init","actions","headless","Media","standalone","app","Video","2026-11-10 10:12:30",false,"---\nname: cometchat-js-v5-sdk\ndescription: \"Add voice & video calling to any web app FROM SCRATCH with the headless CometChat Calls SDK v5 (`@cometchat\u002Fcalls-sdk-javascript@5`) — no prebuilt UI Kit. init→login→generateToken→joinSession, event listeners, in-call actions (mute\u002Fvideo\u002Fscreen-share\u002Frecord\u002Flayout), meet-style session rooms AND 1:1 ringing (Chat SDK signaling + Calls SDK media). Triggers: 'add calling from scratch', 'standalone video call', 'headless calls sdk', 'build my own call UI', 'meeting room join by session id', 'one-on-one ringing call without uikit'.\"\nlicense: \"MIT\"\ncompatibility: \"Modern WebRTC browser (Chrome 72+\u002FFirefox 68+\u002FSafari 12.1+\u002FEdge 79+); HTTPS (or localhost) for getUserMedia; @cometchat\u002Fcalls-sdk-javascript@^5 (5.0.5). 1:1 ringing also needs @cometchat\u002Fchat-sdk-javascript@^4 for signaling. Framework-agnostic (vanilla JS core; React\u002FVue\u002FAngular\u002FNext recipes).\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat calls sdk v5 headless voice video webrtc javascript calling standalone\"\n---\n\n> **Ground truth:** `@cometchat\u002Fcalls-sdk-javascript@5` + catalog `web-calls-v5.json` (the closed symbol list — every `CometChatCalls.*` below exists in it). Official docs: `\u002Fcalls\u002Fjavascript\u002F**` = **v5** · Docs MCP. Fetch exact `SessionSettings` fields, event names, and action-method signatures from the docs (`references\u002Fdocs-map.md`) — never memory. **APPEND to the user's app — additive wiring only** (`RULES.md`). This is the HEADLESS path (no UI Kit); for the prebuilt drop-in call UI use `cometchat-react-v7-calls` instead.\n\n## Companion skills (read first)\n- **Standalone\u002Fheadless entry** — this skill owns its own package (the Calls SDK) and has no `-core` sibling; it is self-contained for meet-style calling.\n- **For 1:1 RINGING only** it also drives the **Chat SDK** (`@cometchat\u002Fchat-sdk-javascript@4`) for call signaling — signatures fetched from docs via `references\u002Fdocs-map.md` (§ \"1:1 RINGING\"). It does NOT depend on the React UI Kit.\n- **Prefer the UI Kit instead?** If the app also wants chat and a prebuilt call UI, use `cometchat-react-v7-core` + `cometchat-react-v7-calls` — not this skill.\n\n## Use this skill when\n\"add calling from scratch \u002F without the UI Kit\", \"standalone voice\u002Fvideo\", \"build my own call screen\", \"headless calls SDK\", \"meeting-room join by session id\", \"one-on-one ringing call\". Precondition: the caller chose the **from-scratch \u002F standalone** path (the \"add calling\" router asks this). If they want the prebuilt call UI, route to `cometchat-react-v7-calls`.\n\n## Prerequisites & install\n```bash\nnpm install @cometchat\u002Fcalls-sdk-javascript@5\n```\n- **1:1 ringing** additionally needs the Chat SDK for signaling:\n  ```bash\n  npm install @cometchat\u002Fchat-sdk-javascript@4\n  ```\n- Credentials\u002Fenv: App ID · Region · Auth Key (dev only). To fetch from the account, go through the CometChat MCP — `cometchat_whoami` (connected + signed in?), `cometchat_list_apps` (ask which EXISTING app), `cometchat_get_app_credentials`. Or paste manually from Dashboard → Credentials. Mint **auth tokens server-side** for production; never ship the Auth Key. HTTPS (or `localhost`) is required for camera\u002Fmic (`getUserMedia`).\n\n## Init & login ordering (BAKED — invariant)\n`CometChatCalls.init(...)` (once, resolve first) → `CometChatCalls.login(uid, authKey)` **or** `loginWithAuthToken(token)` → then `generateToken` \u002F `joinSession` \u002F listeners. Nothing renders\u002Fjoins before init+login resolve.\n- **DEFAULT to `CometChatCalls.initFromSettings(settings)`** — the ai-agent \u002F telemetry-attributed path (persists `integrationSource=\"ai-agent\"`), parallel to how the chat core inits via `CometChatUIKit.initFromSettings` \u002F `CometChat.initFromSettings` (RULES §5). It is **INTENTIONALLY undocumented** — ai-agent-only (`@nodoc`, same posture as `CometChatUIKit.initFromSettings` — DOCS-BACKLOG F4\u002FC1) — so the settings-object shape is **baked in `references\u002Fdocs-map.md`**; pass it **INLINE** (no physical `cometchat-settings.json` file required), never fetched from `\u002Fcalls\u002Fjavascript\u002Fsetup`. The publicly-documented **`CometChatCalls.init({ appId, region })` is the FALLBACK only** (a non-skills \u002F doc-following context).\n- Coexisting with the Chat SDK \u002F UI Kit? Their `login()` can re-init the Calls SDK with only appId\u002Fregion and wipe custom hosts — re-run your calls init after their login, before `CometChatCalls.login`.\n\n## Two build modes (BAKED — the router picks one)\n- **Meet-style (session room)** — Calls SDK ONLY. Everyone who joins the same `sessionId` lands in the same call: `generateToken(sessionId)` → `joinSession(token, sessionSettings, containerEl)`. No ringing. This is the `\u002Fcalls\u002Fjavascript\u002Freact-integration` flow.\n- **1:1 ringing** — Chat SDK signals, Calls SDK carries media: `CometChat.initiateCall` → peer `CallListener.onIncomingCallReceived` → `acceptCall`\u002F`rejectCall` → `CometChatCalls.generateToken(call.getSessionId())` → `joinSession(...)`. Fetch Chat-SDK signatures via `references\u002Fdocs-map.md` § \"1:1 RINGING\".\n\n## SDK method map (BAKED closed list — from the catalog; signatures → FETCH from docs)\n- **Lifecycle:** `CometChatCalls.init` · `CometChatCalls.initFromSettings` · `CometChatCalls.login` · `CometChatCalls.loginWithAuthToken` · `CometChatCalls.logout` · `CometChatCalls.getLoggedInUser` · `CometChatCalls.isUserLoggedIn`\n- **Session:** `CometChatCalls.generateToken` · `CometChatCalls.joinSession` · `CometChatCalls.leaveSession` (`startSession` is **deprecated** → use `joinSession`)\n- **Events:** `CometChatCalls.addEventListener(eventName, cb, { signal? }) → unsubscribe()` (event names: FETCH the full list from `\u002Fcalls\u002Fjavascript\u002Fevents`)\n- **In-call actions** — ⚠️ **for CUSTOM controls ONLY; the default `joinSession` UI already renders all of these** (see the first pitfall). Only reach for them when the user EXPLICITLY asks to replace the built-in controls: `muteAudio`\u002F`unmuteAudio`\u002F`toggleAudio` · `pauseVideo`\u002F`resumeVideo`\u002F`toggleVideo` · `setLayout` · `startRecording`\u002F`stopRecording` · `startScreenSharing`\u002F`stopScreenSharing` · `raiseHand`\u002F`lowerHand` · `switchCamera` · `pinParticipant`\u002F`unpinParticipant` · `showParticipantList`\u002F`hideParticipantList`\n- **Devices:** `getAudioInputDevices` · `getAudioOutputDevices` · `getVideoInputDevices` · `getCurrent*Device`\n- **Call logs:** `CometChatCalls.CallLogRequestBuilder` → `fetchNext()` (paginated; shape → docs)\n- **Constants:** `CometChatCalls.constants.LAYOUT` (`TILE`\u002F`SIDEBAR`\u002F`SPOTLIGHT`) · `.TYPE` (`VOICE`\u002F`VIDEO`) · `.CAMERA_FACING`\n> This map is a **curated highlight, NOT the full surface** — the AUTHORITATIVE closed list is the **`web-calls-v5.json` catalog** (83 symbols; it also carries `toggleHand`\u002F`toggleParticipantList`\u002F`endSessionForAll`\u002F`muteParticipant`\u002F`pauseParticipantVideo`\u002F`setChatButtonUnreadCount`\u002F`switchToVideoCall`, device setters (`setAudioInputDevice`...), the virtual-background methods, `startStreaming`\u002F`stopStreaming` (**RTMP live-streaming** — with `streamUrl`\u002F`streamKey`\u002F`hideStreamingButton` in `SessionSettings`; neither the SKILL map above nor the `\u002Fcalls\u002Fjavascript\u002Factions` doc foregrounds it, but it is real), `startTranscription`\u002F`stopTranscription` (v5.0.5 — see `\u002Fcalls\u002Fjavascript\u002Ftranscription`), and `TranscriptRequestBuilder`, among others). A symbol is real **iff it's in the catalog** — confirm THERE (not just this map), then fetch its exact signature\u002Fparams from the docs page in `references\u002Fdocs-map.md`.\n\n## Listener lifecycle (BAKED)\n`addEventListener` RETURNS an unsubscribe function — collect them and call every one on teardown (React: in the effect cleanup), and `CometChatCalls.leaveSession()` on unmount. Register listeners BEFORE `joinSession`. Never leak. You can also pass an `AbortSignal` via the `{ signal }` option for bulk teardown.\n\n## Least-code recipe (meet-style, framework-agnostic)\n```ts\n\u002F\u002F STRICT-TS-CLEAN: type the settings with the EXPORTED SessionSettings, narrow region.\nimport { CometChatCalls } from \"@cometchat\u002Fcalls-sdk-javascript\";\nimport type { SessionSettings } from \"@cometchat\u002Fcalls-sdk-javascript\"; \u002F\u002F exported; SessionType\u002FLayout are NOT\n\n1. await CometChatCalls.initFromSettings({ appId, region: region as \"us\"|\"eu\"|\"in\", credentials: { authKey: AUTH_KEY }, callsSDK: {}, chatSDK: {}, uiKit: {} }) \u002F\u002F ai-agent telemetry default (integrationSource=\"ai-agent\"); init({appId,region}) is the public-doc fallback\n2. await CometChatCalls.login(uid, AUTH_KEY)               \u002F\u002F or loginWithAuthToken(token)\n3. const { token } = await CometChatCalls.generateToken(sessionId)\n4. const unsub = CometChatCalls.addEventListener(\"onSessionLeft\", () => cleanup())\n5. const callSettings: SessionSettings = { sessionType: \"VIDEO\", layout: \"TILE\" } \u002F\u002F annotate → literals narrow\n   await CometChatCalls.joinSession(token, callSettings, containerEl)\n6. \u002F\u002F NO control buttons needed — joinSession's UI ALREADY renders mute\u002Fvideo\u002Fscreen-share\u002Fraise-hand\u002Fleave.\n7. \u002F\u002F teardown → unsub(); CometChatCalls.leaveSession()\n```\nThe `containerEl` MUST have real dimensions — the SDK renders its call surface into it. Fetch the full `SessionSettings` field list from `\u002Fcalls\u002Fjavascript\u002Fsession-settings`. (In plain JS drop the annotations; the doc pages show that JS form.)\n\n## Framework notes (same SDK, per-framework glue)\nThe recipe above is framework-agnostic; the only per-framework part is WHERE you register listeners \u002F mount the container \u002F tear down. Verified live on React and Angular.\n- **React:** provider or component — init via `CometChatCalls.initFromSettings(...)` (the telemetry-attributed default — `integrationSource=\"ai-agent\"`; `init({appId,region})` is the public-doc fallback), then register listeners + `joinSession` in a `useEffect`; teardown in the effect cleanup (call every unsubscribe + `leaveSession`). Recipe: `\u002Fcalls\u002Fjavascript\u002Freact-integration`.\n- **Angular:** a **DI service** wrapping `CometChatCalls` (init via `CometChatCalls.initFromSettings(...)` — the telemetry-attributed default (`integrationSource=\"ai-agent\"`; `init({appId,region})` is the public-doc fallback) → login, `generateToken`, typed `joinSession`, `leaveSession`; expose readiness via an RxJS `BehaviorSubject`) + a component with a **sized `@ViewChild('callContainer') ElementRef`** container; register listeners BEFORE `joinSession`; teardown in **`ngOnDestroy`** (unsubscribe all + `leaveSession`). Recipe: `\u002Fcalls\u002Fjavascript\u002Fangular-integration` — but ⚠️ THREE things to override:\n  - **(a)** its example wires external Mute\u002FVideo\u002FLeave buttons — **IGNORE them** (pitfall #1: `joinSession`'s UI already has the controls);\n  - **(b)** it targets legacy `@NgModule`\u002F`app.module.ts` — a modern `ng new` is **standalone** (`bootstrapApplication` + `app.config.ts`, class `App`), so use the standalone variant;\n  - **(c) ⚠️ NgZone \u002F change detection (the silent dead-state).** CometChat SDK callbacks — event listeners AND the `login`\u002F`generateToken`\u002F`joinSession` promise resolutions — fire OUTSIDE Angular's zone, so any component state you set inside them **won't trigger change detection** (symptom: readiness\u002Fcall buttons *silently never enable*, even though the SDK succeeded). Fix: drive the template off your `BehaviorSubject` via the **`async` pipe**, AND\u002FOR wrap state writes in **`this.zone.run(() => ...)`** (inject `NgZone`) or call `ChangeDetectorRef.detectChanges()`. Not optional — the app looks broken without it.\n\n## Common pitfalls (BAKED)\n- **Don't duplicate the built-in call controls (the #1 mistake).** `joinSession` renders a COMPLETE call UI — mute, camera on\u002Foff, screen-share, raise-hand, participant list, layout switch, and the red leave\u002Fend button are ALL built into the surface it mounts in `containerEl`. Do **NOT** add your own Mute \u002F Start-video \u002F Share-screen \u002F Leave buttons around the container: they are redundant, duplicate the SDK's own controls, and drift out of sync with the real call state. The `muteAudio`\u002F`pauseVideo`\u002F`leaveSession`\u002F... methods are for CUSTOM controls ONLY — reach for them **just when the user EXPLICITLY asks** to replace the default controls (and hide the built-in ones first via `SessionSettings` — `hideControlPanel` for the whole bar, or per-button flags like `hideToggleAudioButton`\u002F`hideRaiseHandButton`\u002F`hideChatButton`; the canonical recipe is `\u002Fcalls\u002Fjavascript\u002Fcustom-control-panel`, fields on `\u002Fcalls\u002Fjavascript\u002Fsession-settings`). Default = render the call surface and stop.\n- **Zero-dimension container** — `joinSession` mounts into `containerEl`; if it has `height:0` the call renders invisibly. Give it explicit size (e.g. `height: 500px` \u002F `100dvh`).\n- **HTTP (not HTTPS)** — `getUserMedia` needs a secure context; camera\u002Fmic silently fail off `localhost`.\n- **Joining before init+login resolve** — `generateToken`\u002F`joinSession` reject; always `await` init then login first.\n- **Leaked listeners \u002F no `leaveSession`** — every `addEventListener` unsubscribe must run on teardown; call `leaveSession()` on unmount.\n- **`startSession` is deprecated** — use `joinSession`; don't pass the old `CallSettings` builder where a plain `SessionSettings` object is expected.\n- **Host wipe on coexisting Chat-SDK login** — re-init the Calls SDK after the Chat SDK\u002FUI Kit logs in (see Init ordering).\n- **version_conflict** — the Calls SDK is **major 5**, distinct from the Chat SDK's v4; do not \"upgrade\" the Chat SDK to a non-existent v7.\n- **Assuming a signature** — event names, `SessionSettings` fields, and action params are FETCHED from docs, never guessed.\n- **1:1 ringing: `CometChat.Call` used only as a TYPE trips `TS6133`** — in strict TS, importing `CometChat` and referencing `CometChat.Call` in type positions only (never as a value) fails with `'CometChat' is declared but its value is never read`. Import the **concrete type** instead: `import { CometChat } from \"@cometchat\u002Fchat-sdk-javascript\"` for the VALUES you call (`initiateCall`\u002F`acceptCall`\u002F`addCallListener`) and `import type { Call } from \"@cometchat\u002Fchat-sdk-javascript\"` for the type. (Same class as the `SessionSettings`\u002F`CometChatCalls` strict-TS trap.)\n- **Strict-TS widening (the doc's bare-object form doesn't compile as-is)** — the doc pages pass `joinSession(token, { sessionType: \"VIDEO\", layout: \"TILE\" }, el)` and `init({ appId, region })` as plain JS. In a strict-TS app (the stock Vite `react-ts` template: `strict` + `verbatimModuleSyntax` + `noUnusedLocals`) those literals WIDEN to `string` and fail `tsc` (TS2345 vs `SessionSettings`; TS2322 for `region`). Fix: `import type { SessionSettings }` (it's exported; `SessionType`\u002F`Layout` are NOT) and annotate the settings object — `const s: SessionSettings = {...}` (or `satisfies SessionSettings`) — and narrow `region` to `\"us\"|\"eu\"|\"in\"`.\n\n## Verify it works\n- **Tier-1 catalog:** every `CometChatCalls.*` symbol emitted appears in `web-calls-v5.json` (`node test-suite\u002Fscripts\u002Fverify-catalog.mjs --family web-calls-v5`).\n- **Tier-2 fences:** the emit type-checks against the installed `@cometchat\u002Fcalls-sdk-javascript@5` `.d.ts`.\n- **Tier-3b headless smoke:** `node test-suite\u002Fscripts\u002Fsdk-smoke.mjs --family web-calls-v5 [--live|--dry]` runs init→login→generateToken→(join wiring)→listener-teardown. Media\u002F`joinSession` needs a real WebRTC\u002FDOM context, so the node smoke covers the token+listener round-trip (`--dry` proves wiring without a backend); the actual call render is verified in a browser harness. Flag \"dry-mock only, not live-certified\" honestly where true.\n","> **Ground truth:** `@cometchat\u002Fcalls-sdk-javascript@5` + catalog `web-calls-v5.json` (the closed symbol list — every `CometChatCalls.*` below exists in it). Official docs: `\u002Fcalls\u002Fjavascript\u002F**` = **v5** · Docs MCP. Fetch exact `SessionSettings` fields, event names, and action-method signatures from the docs (`references\u002Fdocs-map.md`) — never memory. **APPEND to the user's app — additive wiring only** (`RULES.md`). This is the HEADLESS path (no UI Kit); for the prebuilt drop-in call UI use `cometchat-react-v7-calls` instead.\n\n## Companion skills (read first)\n- **Standalone\u002Fheadless entry** — this skill owns its own package (the Calls SDK) and has no `-core` sibling; it is self-contained for meet-style calling.\n- **For 1:1 RINGING only** it also drives the **Chat SDK** (`@cometchat\u002Fchat-sdk-javascript@4`) for call signaling — signatures fetched from docs via `references\u002Fdocs-map.md` (§ \"1:1 RINGING\"). It does NOT depend on the React UI Kit.\n- **Prefer the UI Kit instead?** If the app also wants chat and a prebuilt call UI, use `cometchat-react-v7-core` + `cometchat-react-v7-calls` — not this skill.\n\n## Use this skill when\n\"add calling from scratch \u002F without the UI Kit\", \"standalone voice\u002Fvideo\", \"build my own call screen\", \"headless calls SDK\", \"meeting-room join by session id\", \"one-on-one ringing call\". Precondition: the caller chose the **from-scratch \u002F standalone** path (the \"add calling\" router asks this). If they want the prebuilt call UI, route to `cometchat-react-v7-calls`.\n\n## Prerequisites & install\n```bash\nnpm install @cometchat\u002Fcalls-sdk-javascript@5\n```\n- **1:1 ringing** additionally needs the Chat SDK for signaling:\n  ```bash\n  npm install @cometchat\u002Fchat-sdk-javascript@4\n  ```\n- Credentials\u002Fenv: App ID · Region · Auth Key (dev only). To fetch from the account, go through the CometChat MCP — `cometchat_whoami` (connected + signed in?), `cometchat_list_apps` (ask which EXISTING app), `cometchat_get_app_credentials`. Or paste manually from Dashboard → Credentials. Mint **auth tokens server-side** for production; never ship the Auth Key. HTTPS (or `localhost`) is required for camera\u002Fmic (`getUserMedia`).\n\n## Init & login ordering (BAKED — invariant)\n`CometChatCalls.init(...)` (once, resolve first) → `CometChatCalls.login(uid, authKey)` **or** `loginWithAuthToken(token)` → then `generateToken` \u002F `joinSession` \u002F listeners. Nothing renders\u002Fjoins before init+login resolve.\n- **DEFAULT to `CometChatCalls.initFromSettings(settings)`** — the ai-agent \u002F telemetry-attributed path (persists `integrationSource=\"ai-agent\"`), parallel to how the chat core inits via `CometChatUIKit.initFromSettings` \u002F `CometChat.initFromSettings` (RULES §5). It is **INTENTIONALLY undocumented** — ai-agent-only (`@nodoc`, same posture as `CometChatUIKit.initFromSettings` — DOCS-BACKLOG F4\u002FC1) — so the settings-object shape is **baked in `references\u002Fdocs-map.md`**; pass it **INLINE** (no physical `cometchat-settings.json` file required), never fetched from `\u002Fcalls\u002Fjavascript\u002Fsetup`. The publicly-documented **`CometChatCalls.init({ appId, region })` is the FALLBACK only** (a non-skills \u002F doc-following context).\n- Coexisting with the Chat SDK \u002F UI Kit? Their `login()` can re-init the Calls SDK with only appId\u002Fregion and wipe custom hosts — re-run your calls init after their login, before `CometChatCalls.login`.\n\n## Two build modes (BAKED — the router picks one)\n- **Meet-style (session room)** — Calls SDK ONLY. Everyone who joins the same `sessionId` lands in the same call: `generateToken(sessionId)` → `joinSession(token, sessionSettings, containerEl)`. No ringing. This is the `\u002Fcalls\u002Fjavascript\u002Freact-integration` flow.\n- **1:1 ringing** — Chat SDK signals, Calls SDK carries media: `CometChat.initiateCall` → peer `CallListener.onIncomingCallReceived` → `acceptCall`\u002F`rejectCall` → `CometChatCalls.generateToken(call.getSessionId())` → `joinSession(...)`. Fetch Chat-SDK signatures via `references\u002Fdocs-map.md` § \"1:1 RINGING\".\n\n## SDK method map (BAKED closed list — from the catalog; signatures → FETCH from docs)\n- **Lifecycle:** `CometChatCalls.init` · `CometChatCalls.initFromSettings` · `CometChatCalls.login` · `CometChatCalls.loginWithAuthToken` · `CometChatCalls.logout` · `CometChatCalls.getLoggedInUser` · `CometChatCalls.isUserLoggedIn`\n- **Session:** `CometChatCalls.generateToken` · `CometChatCalls.joinSession` · `CometChatCalls.leaveSession` (`startSession` is **deprecated** → use `joinSession`)\n- **Events:** `CometChatCalls.addEventListener(eventName, cb, { signal? }) → unsubscribe()` (event names: FETCH the full list from `\u002Fcalls\u002Fjavascript\u002Fevents`)\n- **In-call actions** — ⚠️ **for CUSTOM controls ONLY; the default `joinSession` UI already renders all of these** (see the first pitfall). Only reach for them when the user EXPLICITLY asks to replace the built-in controls: `muteAudio`\u002F`unmuteAudio`\u002F`toggleAudio` · `pauseVideo`\u002F`resumeVideo`\u002F`toggleVideo` · `setLayout` · `startRecording`\u002F`stopRecording` · `startScreenSharing`\u002F`stopScreenSharing` · `raiseHand`\u002F`lowerHand` · `switchCamera` · `pinParticipant`\u002F`unpinParticipant` · `showParticipantList`\u002F`hideParticipantList`\n- **Devices:** `getAudioInputDevices` · `getAudioOutputDevices` · `getVideoInputDevices` · `getCurrent*Device`\n- **Call logs:** `CometChatCalls.CallLogRequestBuilder` → `fetchNext()` (paginated; shape → docs)\n- **Constants:** `CometChatCalls.constants.LAYOUT` (`TILE`\u002F`SIDEBAR`\u002F`SPOTLIGHT`) · `.TYPE` (`VOICE`\u002F`VIDEO`) · `.CAMERA_FACING`\n> This map is a **curated highlight, NOT the full surface** — the AUTHORITATIVE closed list is the **`web-calls-v5.json` catalog** (83 symbols; it also carries `toggleHand`\u002F`toggleParticipantList`\u002F`endSessionForAll`\u002F`muteParticipant`\u002F`pauseParticipantVideo`\u002F`setChatButtonUnreadCount`\u002F`switchToVideoCall`, device setters (`setAudioInputDevice`...), the virtual-background methods, `startStreaming`\u002F`stopStreaming` (**RTMP live-streaming** — with `streamUrl`\u002F`streamKey`\u002F`hideStreamingButton` in `SessionSettings`; neither the SKILL map above nor the `\u002Fcalls\u002Fjavascript\u002Factions` doc foregrounds it, but it is real), `startTranscription`\u002F`stopTranscription` (v5.0.5 — see `\u002Fcalls\u002Fjavascript\u002Ftranscription`), and `TranscriptRequestBuilder`, among others). A symbol is real **iff it's in the catalog** — confirm THERE (not just this map), then fetch its exact signature\u002Fparams from the docs page in `references\u002Fdocs-map.md`.\n\n## Listener lifecycle (BAKED)\n`addEventListener` RETURNS an unsubscribe function — collect them and call every one on teardown (React: in the effect cleanup), and `CometChatCalls.leaveSession()` on unmount. Register listeners BEFORE `joinSession`. Never leak. You can also pass an `AbortSignal` via the `{ signal }` option for bulk teardown.\n\n## Least-code recipe (meet-style, framework-agnostic)\n```ts\n\u002F\u002F STRICT-TS-CLEAN: type the settings with the EXPORTED SessionSettings, narrow region.\nimport { CometChatCalls } from \"@cometchat\u002Fcalls-sdk-javascript\";\nimport type { SessionSettings } from \"@cometchat\u002Fcalls-sdk-javascript\"; \u002F\u002F exported; SessionType\u002FLayout are NOT\n\n1. await CometChatCalls.initFromSettings({ appId, region: region as \"us\"|\"eu\"|\"in\", credentials: { authKey: AUTH_KEY }, callsSDK: {}, chatSDK: {}, uiKit: {} }) \u002F\u002F ai-agent telemetry default (integrationSource=\"ai-agent\"); init({appId,region}) is the public-doc fallback\n2. await CometChatCalls.login(uid, AUTH_KEY)               \u002F\u002F or loginWithAuthToken(token)\n3. const { token } = await CometChatCalls.generateToken(sessionId)\n4. const unsub = CometChatCalls.addEventListener(\"onSessionLeft\", () => cleanup())\n5. const callSettings: SessionSettings = { sessionType: \"VIDEO\", layout: \"TILE\" } \u002F\u002F annotate → literals narrow\n   await CometChatCalls.joinSession(token, callSettings, containerEl)\n6. \u002F\u002F NO control buttons needed — joinSession's UI ALREADY renders mute\u002Fvideo\u002Fscreen-share\u002Fraise-hand\u002Fleave.\n7. \u002F\u002F teardown → unsub(); CometChatCalls.leaveSession()\n```\nThe `containerEl` MUST have real dimensions — the SDK renders its call surface into it. Fetch the full `SessionSettings` field list from `\u002Fcalls\u002Fjavascript\u002Fsession-settings`. (In plain JS drop the annotations; the doc pages show that JS form.)\n\n## Framework notes (same SDK, per-framework glue)\nThe recipe above is framework-agnostic; the only per-framework part is WHERE you register listeners \u002F mount the container \u002F tear down. Verified live on React and Angular.\n- **React:** provider or component — init via `CometChatCalls.initFromSettings(...)` (the telemetry-attributed default — `integrationSource=\"ai-agent\"`; `init({appId,region})` is the public-doc fallback), then register listeners + `joinSession` in a `useEffect`; teardown in the effect cleanup (call every unsubscribe + `leaveSession`). Recipe: `\u002Fcalls\u002Fjavascript\u002Freact-integration`.\n- **Angular:** a **DI service** wrapping `CometChatCalls` (init via `CometChatCalls.initFromSettings(...)` — the telemetry-attributed default (`integrationSource=\"ai-agent\"`; `init({appId,region})` is the public-doc fallback) → login, `generateToken`, typed `joinSession`, `leaveSession`; expose readiness via an RxJS `BehaviorSubject`) + a component with a **sized `@ViewChild('callContainer') ElementRef`** container; register listeners BEFORE `joinSession`; teardown in **`ngOnDestroy`** (unsubscribe all + `leaveSession`). Recipe: `\u002Fcalls\u002Fjavascript\u002Fangular-integration` — but ⚠️ THREE things to override:\n  - **(a)** its example wires external Mute\u002FVideo\u002FLeave buttons — **IGNORE them** (pitfall #1: `joinSession`'s UI already has the controls);\n  - **(b)** it targets legacy `@NgModule`\u002F`app.module.ts` — a modern `ng new` is **standalone** (`bootstrapApplication` + `app.config.ts`, class `App`), so use the standalone variant;\n  - **(c) ⚠️ NgZone \u002F change detection (the silent dead-state).** CometChat SDK callbacks — event listeners AND the `login`\u002F`generateToken`\u002F`joinSession` promise resolutions — fire OUTSIDE Angular's zone, so any component state you set inside them **won't trigger change detection** (symptom: readiness\u002Fcall buttons *silently never enable*, even though the SDK succeeded). Fix: drive the template off your `BehaviorSubject` via the **`async` pipe**, AND\u002FOR wrap state writes in **`this.zone.run(() => ...)`** (inject `NgZone`) or call `ChangeDetectorRef.detectChanges()`. Not optional — the app looks broken without it.\n\n## Common pitfalls (BAKED)\n- **Don't duplicate the built-in call controls (the #1 mistake).** `joinSession` renders a COMPLETE call UI — mute, camera on\u002Foff, screen-share, raise-hand, participant list, layout switch, and the red leave\u002Fend button are ALL built into the surface it mounts in `containerEl`. Do **NOT** add your own Mute \u002F Start-video \u002F Share-screen \u002F Leave buttons around the container: they are redundant, duplicate the SDK's own controls, and drift out of sync with the real call state. The `muteAudio`\u002F`pauseVideo`\u002F`leaveSession`\u002F... methods are for CUSTOM controls ONLY — reach for them **just when the user EXPLICITLY asks** to replace the default controls (and hide the built-in ones first via `SessionSettings` — `hideControlPanel` for the whole bar, or per-button flags like `hideToggleAudioButton`\u002F`hideRaiseHandButton`\u002F`hideChatButton`; the canonical recipe is `\u002Fcalls\u002Fjavascript\u002Fcustom-control-panel`, fields on `\u002Fcalls\u002Fjavascript\u002Fsession-settings`). Default = render the call surface and stop.\n- **Zero-dimension container** — `joinSession` mounts into `containerEl`; if it has `height:0` the call renders invisibly. Give it explicit size (e.g. `height: 500px` \u002F `100dvh`).\n- **HTTP (not HTTPS)** — `getUserMedia` needs a secure context; camera\u002Fmic silently fail off `localhost`.\n- **Joining before init+login resolve** — `generateToken`\u002F`joinSession` reject; always `await` init then login first.\n- **Leaked listeners \u002F no `leaveSession`** — every `addEventListener` unsubscribe must run on teardown; call `leaveSession()` on unmount.\n- **`startSession` is deprecated** — use `joinSession`; don't pass the old `CallSettings` builder where a plain `SessionSettings` object is expected.\n- **Host wipe on coexisting Chat-SDK login** — re-init the Calls SDK after the Chat SDK\u002FUI Kit logs in (see Init ordering).\n- **version_conflict** — the Calls SDK is **major 5**, distinct from the Chat SDK's v4; do not \"upgrade\" the Chat SDK to a non-existent v7.\n- **Assuming a signature** — event names, `SessionSettings` fields, and action params are FETCHED from docs, never guessed.\n- **1:1 ringing: `CometChat.Call` used only as a TYPE trips `TS6133`** — in strict TS, importing `CometChat` and referencing `CometChat.Call` in type positions only (never as a value) fails with `'CometChat' is declared but its value is never read`. Import the **concrete type** instead: `import { CometChat } from \"@cometchat\u002Fchat-sdk-javascript\"` for the VALUES you call (`initiateCall`\u002F`acceptCall`\u002F`addCallListener`) and `import type { Call } from \"@cometchat\u002Fchat-sdk-javascript\"` for the type. (Same class as the `SessionSettings`\u002F`CometChatCalls` strict-TS trap.)\n- **Strict-TS widening (the doc's bare-object form doesn't compile as-is)** — the doc pages pass `joinSession(token, { sessionType: \"VIDEO\", layout: \"TILE\" }, el)` and `init({ appId, region })` as plain JS. In a strict-TS app (the stock Vite `react-ts` template: `strict` + `verbatimModuleSyntax` + `noUnusedLocals`) those literals WIDEN to `string` and fail `tsc` (TS2345 vs `SessionSettings`; TS2322 for `region`). Fix: `import type { SessionSettings }` (it's exported; `SessionType`\u002F`Layout` are NOT) and annotate the settings object — `const s: SessionSettings = {...}` (or `satisfies SessionSettings`) — and narrow `region` to `\"us\"|\"eu\"|\"in\"`.\n\n## Verify it works\n- **Tier-1 catalog:** every `CometChatCalls.*` symbol emitted appears in `web-calls-v5.json` (`node test-suite\u002Fscripts\u002Fverify-catalog.mjs --family web-calls-v5`).\n- **Tier-2 fences:** the emit type-checks against the installed `@cometchat\u002Fcalls-sdk-javascript@5` `.d.ts`.\n- **Tier-3b headless smoke:** `node test-suite\u002Fscripts\u002Fsdk-smoke.mjs --family web-calls-v5 [--live|--dry]` runs init→login→generateToken→(join wiring)→listener-teardown. Media\u002F`joinSession` needs a real WebRTC\u002FDOM context, so the node smoke covers the token+listener round-trip (`--dry` proves wiring without a backend); the actual call render is verified in a browser harness. Flag \"dry-mock only, not live-certified\" honestly where true.\n",{"name":5,"license":15,"metadata":60,"description":7,"compatibility":64},{"tags":61,"author":62,"version":63},"cometchat calls sdk v5 headless voice video webrtc javascript calling standalone","CometChat","1.0.0","Modern WebRTC browser (Chrome 72+\u002FFirefox 68+\u002FSafari 12.1+\u002FEdge 79+); HTTPS (or localhost) for getUserMedia; @cometchat\u002Fcalls-sdk-javascript@^5 (5.0.5). 1:1 ringing also needs @cometchat\u002Fchat-sdk-javascript@^4 for signaling. Framework-agnostic (vanilla JS core; React\u002FVue\u002FAngular\u002FNext recipes).","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-js-v5-sdk",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-js-v5-sdk",{"tool":81,"command":82},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-js-v5-sdk",{"tool":84,"command":85},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-js-v5-sdk","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-js-v5-sdk\u002FSKILL.md",true,[89],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fdocs-map.md","REFERENCE","参考文档",10230,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-js-v5-sdk\u002Freferences\u002Fdocs-map.md",[96,105,113,121,129,137],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":104},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":104},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":104},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":104},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":104},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":104},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]