@okostream/mcp 0.12.15 → 0.12.16

package/dist/server.js

@@ -116291,7 +116291,7 @@ function sanitizeScopes(scopes) {
 }
 
 // build/version.js
-var OKO_MCP_VERSION = "0.12.15";
+var OKO_MCP_VERSION = "0.12.16";
 
 // build/auth.js
 var state = null;
@@ -118812,7 +118812,7 @@ function registerEventTools(server2) {
       returns: "event document fields plus id and public event URL. The event's access composition (the historical uid arrays) is never returned; ask oko_list_workspace_access for who has access.",
       examples: ["Use after oko_create_webinar to verify setup and return the event URL to the user."],
       notes: [
-        "blocks.chat.mode and blocks.chat.visibility are both legacy: the event page reads neither \u2014 the chat panel exists exactly when blocks.chat.enabled is true, and sending is opened or closed live with oko_set_chat_mode. Ignore both fields."
+        "blocks.chat: the panel exists exactly when blocks.chat.enabled is true. blocks.chat.intake says whether it ACCEPTS MESSAGES before anyone touches the live control \u2014 closed (default), open, schedule (at the event time), or session (while an analytics session runs); oko_set_chat_mode overrides it live. blocks.chat.mode and blocks.chat.visibility are legacy and read by nobody \u2014 ignore those two."
       ]
     }),
     inputSchema: { eventId: eventIdField },
@@ -118857,7 +118857,7 @@ function registerEventTools(server2) {
         "workspaceId: optional workspace id; omitted means personal workspace.",
         "videoUrl: optional iframe/source/player URL; normalized by OKO.",
         "eventDate: optional ISO datetime.",
-        "chatEnabled: whether the chat block is enabled at creation."
+        "chatEnabled: whether the chat block is on the page at creation. It does NOT open message sending: a new event starts with intake closed, so the chat is visible and silent until the organizer opens it (oko_set_chat_mode) or sets blocks.chat.intake."
       ],
       returns: "new event id, public event URL, and workspaceId.",
       examples: ["Use for a complete create flow, then call oko_configure_blocks and oko_get_event."],
@@ -118870,7 +118870,7 @@ function registerEventTools(server2) {
       eventDate: external_exports.string().datetime().nullable().optional().describe("Optional webinar datetime in ISO format."),
       speakerName: external_exports.string().max(160).nullable().optional().describe("Optional speaker display name."),
       description: external_exports.string().max(3e3).nullable().optional().describe('Optional event description shown under the speaker name. Omit or pass "" for none; the literal text "null" is rejected.'),
-      chatEnabled: external_exports.boolean().default(false).describe("Whether the chat block starts enabled.")
+      chatEnabled: external_exports.boolean().default(false).describe("Whether the chat block is on the page at creation; message sending stays closed until opened.")
     },
     outputSchema: createWebinarOutputSchema,
     annotations: writeTool
@@ -118984,6 +118984,7 @@ function registerEventTools(server2) {
       returns: "event id and the list of Firestore fields updated.",
       examples: ["Use after oko_create_webinar to enable chat, bind a CTA/form, and configure other audience blocks."],
       notes: [
+        '\u{1F534} "Turn off the chat" is ambiguous, and the two meanings are not close. chat.enabled=false REMOVES the chat block from the page together with every message people wrote \u2014 irreversible for the audience, and almost never what someone asks for mid-webinar. Stopping new messages is a different tool: oko_set_chat_mode with mode="off" leaves the block and the whole history in place. When the organizer says "turn off the chat", "close the chat", "stop the chat", "disable chat", assume they mean the mode, and ASK before removing the block. The same trap in reverse: "turn the chat back on" after a pause means mode="public", not this field.',
         "A block toggle and its image are independent: enabling a block here works with an image already uploaded via oko_upload_image, and uploading an image never enables the block by itself.",
         "promoBanner has no text field by design: the banner is image+link. blocks.promoBanner.text seen in event documents is legacy and is never rendered on the event page.",
         'videoPlaceholder.enabled only allows the placeholder; viewers see it after oko_set_block_visibility with block "placeholder" and visible true (a live override, stored outside the event document). Chat, CTA, banner and cards appear as soon as they are enabled here.',
@@ -118994,7 +118995,11 @@ function registerEventTools(server2) {
     }),
     inputSchema: {
       eventId: eventIdField,
-      chat: external_exports.object({ enabled: external_exports.boolean().optional(), visibility: external_exports.enum(["always", "hidden"]).optional() }).optional(),
+      chat: external_exports.object({
+        enabled: external_exports.boolean().optional().describe("Whether the chat block is ON THE PAGE. false removes it together with the message history \u2014 see the note above before using it."),
+        intake: external_exports.enum(["closed", "open", "schedule", "session"]).optional().describe("When the chat starts accepting messages before any live override: closed (default \u2014 visible and silent until opened), open, schedule (at the event time), session (while an analytics session runs)."),
+        visibility: external_exports.enum(["always", "hidden"]).optional()
+      }).optional(),
       promoBanner: external_exports.object({ enabled: external_exports.boolean().optional(), link: external_exports.string().max(1e3).optional(), visibility: external_exports.enum(["always", "hidden"]).optional(), formId: external_exports.string().nullable().optional() }).optional(),
       primaryCta: external_exports.object({ enabled: external_exports.boolean().optional(), visibility: external_exports.enum(["always", "hidden"]).optional(), title: external_exports.string().nullable().optional(), text: external_exports.string().nullable().optional(), buttonLabel: external_exports.string().nullable().optional(), buttonUrl: external_exports.string().nullable().optional(), formId: external_exports.string().nullable().optional() }).optional(),
       videoPlaceholder: external_exports.object({ enabled: external_exports.boolean().optional(), mode: external_exports.enum(["glass", "image"]).optional(), title: external_exports.string().nullable().optional(), subtitle: external_exports.string().nullable().optional(), showTimer: external_exports.boolean().optional() }).optional(),
@@ -119013,6 +119018,8 @@ function registerEventTools(server2) {
     const patch = {};
     if (args.chat?.enabled !== void 0)
       patch["blocks.chat.enabled"] = args.chat.enabled;
+    if (args.chat?.intake !== void 0)
+      patch["blocks.chat.intake"] = args.chat.intake;
     if (args.chat?.visibility !== void 0)
       patch["blocks.chat.visibility"] = args.chat.visibility;
     if (args.promoBanner?.enabled !== void 0)
@@ -119071,6 +119078,12 @@ function registerEventTools(server2) {
     if (args.chat?.visibility !== void 0) {
       hints.push("blocks.chat.visibility was stored but the event page does not read it: the chat panel exists exactly when blocks.chat.enabled is true, and sending is opened or closed live with oko_set_chat_mode. Drop the field.");
     }
+    if (args.chat?.enabled === false) {
+      hints.push('The chat block is now off in setup: it is gone from the page for everyone, together with every message the audience wrote. If the goal was only to stop NEW messages \u2014 which is what "turn off the chat" usually means during or after a webinar \u2014 re-enable it here and use oko_set_chat_mode with mode "off" instead: the block and the whole history stay in place. Worth confirming with the organizer which of the two they meant.');
+    }
+    if (args.chat?.enabled === true && args.chat?.intake === void 0) {
+      hints.push('The chat block is on the page, but message sending stays closed until it is opened: a chat nobody opened is silent by default. Open it now with oko_set_chat_mode mode "public", or set blocks.chat.intake to open / schedule / session so it opens by itself.');
+    }
     const currentBlocks = current.blocks && typeof current.blocks === "object" ? current.blocks : {};
     const bannerHasImage = Boolean(safeString(currentBlocks.promoBanner?.imageUrl) || safeString(currentBlocks.promoBanner?.imageMasterUrl));
     if (args.promoBanner?.enabled === false && bannerHasImage) {
@@ -120038,16 +120051,17 @@ function registerLiveTools(server2) {
   server2.registerTool("oko_set_chat_mode", {
     title: "Set chat mode",
     description: toolDescription({
-      summary: "Open or close chat sending on the public event page.",
+      summary: "Open or close MESSAGE SENDING on the event page. The chat block itself stays where it is.",
       exampleCall: { "eventId": "Kx9pQ2mR7tL4vB8nW3cY", "mode": "off", "confirm": true },
       args: [
         "eventId: event to control.",
-        "mode: public (anyone can send), off (input closed, history stays visible), or null to reset to the product default (public).",
+        "mode: public (anyone can send), off (input closed, history stays visible), or null to fall back to the event's own setting (blocks.chat.intake, closed unless the organizer chose otherwise).",
         "confirm: must be true."
       ],
       returns: "eventId and the effective chat mode.",
-      examples: ['Use mode="off" to pause a chat storm; use mode=null or "public" to reopen.'],
+      examples: ['Use mode="off" to pause a chat storm; use mode="public" to reopen.'],
       notes: [
+        '\u{1F534} "Turn off the chat" means one of TWO different things, and picking the wrong one destroys what people wrote. THIS tool stops new messages: the block stays on the page, history stays readable, nothing is lost. The other one \u2014 oko_configure_blocks with chat.enabled=false \u2014 removes the block from the page together with the whole conversation. When the organizer says "turn off the chat", "close the chat", "stop the chat", "mute the chat" during or after a webinar, they almost always mean THIS tool. Ask before removing the block.',
         'This is the full replacement for the legacy pause via oko_set_block_visibility(block="chat"): prefer oko_set_chat_mode.',
         "There are no other levels: the server has exactly two states, sending open or closed. History is always visible; the mode never restricts who can read or hides anyone's messages."
       ]
@@ -120057,7 +120071,7 @@ function registerLiveTools(server2) {
       // LD5a-2 / A8 (owner decision 03.09): "auth" and "owner" were promised
       // here and enforced nowhere — the rule and every client only check
       // `mode !== "off"`. The contract now says what the server does.
-      mode: external_exports.enum(["public", "off"]).nullable().describe("Chat mode: public or off; null resets the override to the default."),
+      mode: external_exports.enum(["public", "off"]).nullable().describe("Chat mode: public or off; null drops the live override and falls back to the event setting."),
       confirm: external_exports.boolean().optional().describe("Required true to change the live chat mode.")
     },
     outputSchema: basicEventOutputSchema,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@okostream/mcp",
-  "version": "0.12.15",
+  "version": "0.12.16",
   "description": "Control OKO Stream webinars from Claude, Codex, and other MCP clients.",
   "license": "UNLICENSED",
   "author": {