claude-threads 1.40.2 → 1.41.0

package/dist/mcp/mcp-server.js

@@ -15692,6 +15692,7 @@ var require_constants2 = __commonJS(function(exports, module) {
 
 // node_modules/ws/lib/buffer-util.js
 var require_buffer_util = __commonJS(function(exports, module) {
+  var { websocketMask, websocketUnmask } = __require("http");
   var { EMPTY_BUFFER } = require_constants2();
   var FastBuffer = Buffer[Symbol.species];
   function concat(list, totalLength) {
@@ -15749,7 +15750,20 @@ var require_buffer_util = __commonJS(function(exports, module) {
     toBuffer,
     unmask: _unmask
   };
-  if (!process.env.WS_NO_BUFFER_UTIL) {
+  if (websocketMask) {
+    module.exports.mask = function(source, mask, output, offset, length) {
+      if (length < 24)
+        _mask(source, mask, output, offset, length);
+      else
+        websocketMask(source, mask, output, offset, length);
+    };
+    module.exports.unmask = function(buffer, mask) {
+      if (buffer.length < 24)
+        _unmask(buffer, mask);
+      else
+        websocketUnmask(buffer, mask);
+    };
+  } else if (!process.env.WS_NO_BUFFER_UTIL) {
     try {
       const bufferUtil = (()=>{throw new Error("Cannot require module "+"bufferutil");})();
       module.exports.mask = function(source, mask2, output, offset, length) {
@@ -16737,13 +16751,16 @@ var require_sender = __commonJS(function(exports, module) {
         target[2] = target[3] = 0;
         target.writeUIntBE(dataLength, 4, 6);
       }
-      if (!options.mask)
-        return [target, data];
+      if (!options.mask) {
+        return dataLength ? [target, data] : [target];
+      }
       target[1] |= 128;
       target[offset - 4] = mask[0];
       target[offset - 3] = mask[1];
       target[offset - 2] = mask[2];
       target[offset - 1] = mask[3];
+      if (!dataLength)
+        return [target];
       if (skipMasking)
         return [target, data];
       if (merge) {
@@ -17803,9 +17820,14 @@ var require_websocket = __commonJS(function(exports, module) {
       opts.auth = `${parsedUrl.username}:${parsedUrl.password}`;
     }
     if (isIpcUrl) {
-      const parts = opts.path.split(":");
-      opts.socketPath = parts[0];
-      opts.path = parts[1];
+      const i = opts.path.indexOf(":");
+      if (i === -1) {
+        opts.socketPath = opts.path;
+        opts.path = "";
+      } else {
+        opts.socketPath = opts.path.slice(0, i);
+        opts.path = opts.path.slice(i + 1);
+      }
     }
     let req;
     if (opts.followRedirects) {
@@ -34277,12 +34299,13 @@ function truncateAtCodePoint(text, max) {
     return { text, truncated: false };
   return { text: points.slice(0, max).join(""), truncated: true };
 }
+var COMMAND_BLOCK_MIN_LENGTH = 120;
 var bashToolFormatter = {
   toolNames: ["Bash"],
   format(toolName, input, options) {
     if (toolName !== "Bash")
       return null;
-    const { formatter, maxCommandLength = 50, worktreeInfo } = options;
+    const { formatter, detailed = false, maxCommandLength = 50, worktreeInfo } = options;
     let cmd = input.command || "";
     if (worktreeInfo?.path) {
       cmd = cmd.replace(new RegExp(escapeRegExp(worktreeInfo.path), "g"), `[${worktreeInfo.branch}]`);
@@ -34292,8 +34315,14 @@ var bashToolFormatter = {
     const permission = truncateAtCodePoint(cmd, PERMISSION_COMMAND_MAX);
     const permissionCmd = escapeCodeBlockContent(permission.text) + (permission.truncated ? `
 [... truncated]` : "");
+    let display = `\uD83D\uDCBB ${formatter.formatBold("Bash")} ${formatter.formatCode(displayCmd + (truncated ? "..." : ""))}`;
+    if (detailed && truncated && (cmd.length > COMMAND_BLOCK_MIN_LENGTH || cmd.includes(`
+`))) {
+      display += `
+${formatter.formatCodeBlock(permissionCmd, "bash")}`;
+    }
     return {
-      display: `\uD83D\uDCBB ${formatter.formatBold("Bash")} ${formatter.formatCode(displayCmd + (truncated ? "..." : ""))}`,
+      display,
       permissionText: `\uD83D\uDCBB ${formatter.formatBold("Bash")}
 ${formatter.formatCodeBlock(permissionCmd, "bash")}`,
       isDestructive: true
@@ -35087,8 +35116,12 @@ function formatBytes(bytes) {
 
 // src/operations/streaming/handler.ts
 var log9 = createLogger("streaming");
+
+// src/operations/user-attribution/formatter.ts
+var speakersBySession = new WeakMap;
 // src/operations/message-manager.ts
 var log10 = createLogger("msg-mgr");
+var REACTION_ANCHOR_TYPES = new Set(["content", "task_list", "subagent"]);
 // src/persistence/session-store.ts
 init_logger();
 import { join as join3 } from "path";
@@ -38847,6 +38880,10 @@ var LOGS_BASE_DIR = join4(stateHome(), ".claude-threads", "logs");
 // src/operations/bug-report/handler.ts
 var piiRedactor = new Redactor({ aggressive: true });
 var MAX_SCREENSHOT_BYTES = 10 * 1024 * 1024;
+// src/session/lifecycle-delivery.ts
+init_logger();
+var sessionLog2 = createSessionLog(createLogger("lifecycle"));
+
 // src/mcp/decision-bridge.ts
 import { createServer, createConnection } from "node:net";
 var MAX_BRIDGE_REQUEST_BYTES = 1024 * 1024;
@@ -39740,13 +39777,13 @@ var log19 = createLogger("tags");
 // src/session/metadata-suggestions.ts
 init_logger();
 var log20 = createLogger("session");
-var sessionLog2 = createSessionLog(log20);
+var sessionLog3 = createSessionLog(log20);
 
 // src/operations/context-prompt/handler.ts
 init_emoji();
 init_logger();
 var log21 = createLogger("context");
-var sessionLog3 = createSessionLog(log21);
+var sessionLog4 = createSessionLog(log21);
 var contextPromptTimeouts = new Map;
 var contextPromptFiles = new Map;
 // src/memory/store.ts
@@ -39792,21 +39829,21 @@ var log27 = createLogger("watches");
 // src/operations/commands/guards.ts
 init_logger();
 var log28 = createLogger("commands");
-var sessionLog4 = createSessionLog(log28);
+var sessionLog5 = createSessionLog(log28);
 
 // src/operations/commands/automation.ts
 init_logger();
 var log29 = createLogger("commands");
-var sessionLog5 = createSessionLog(log29);
+var sessionLog6 = createSessionLog(log29);
 
 // src/operations/agent-actions/handler.ts
 init_logger();
 var log30 = createLogger("agent-actions");
-var sessionLog6 = createSessionLog(log30);
+var sessionLog7 = createSessionLog(log30);
 
 // src/session/lifecycle.ts
 var log31 = createLogger("lifecycle");
-var sessionLog7 = createSessionLog(log31);
+var sessionLog8 = createSessionLog(log31);
 var _inFlightSessionStarts = new Map;
 var CHAT_PLATFORM_PROMPT = generateChatPlatformPrompt();
 
@@ -39830,11 +39867,11 @@ var DEFAULT_FILE3 = join9(DEFAULT_CONFIG_DIR2, "github-emails.yaml");
 
 // src/operations/commands/handler.ts
 var log33 = createLogger("commands");
-var sessionLog8 = createSessionLog(log33);
+var sessionLog9 = createSessionLog(log33);
 // src/operations/commands/memory.ts
 init_logger();
 var log34 = createLogger("commands");
-var sessionLog9 = createSessionLog(log34);
+var sessionLog10 = createSessionLog(log34);
 // src/operations/suggestions/branch.ts
 init_quick_query();
 init_logger();
@@ -39847,11 +39884,11 @@ var log35 = createLogger("branch");
 init_cli();
 init_logger();
 var log36 = createLogger("worktree");
-var sessionLog10 = createSessionLog(log36);
+var sessionLog11 = createSessionLog(log36);
 // src/operations/events/handler.ts
 init_logger();
 var log37 = createLogger("events");
-var sessionLog11 = createSessionLog(log37);
+var sessionLog12 = createSessionLog(log37);
 // src/operations/monitor/handler.ts
 init_logger();
 var log38 = createLogger("monitor");

package/docs/CONFIGURATION.md

@@ -173,6 +173,7 @@ What happens: every `audio/*` attachment (or a file with an audio extension when
 | `sessionHeader` | No | Per-thread header visibility: `full` (default) / `minimal` (status bar only) / `hidden` (no header post) |
 | `stickyMessage` | No | Channel sticky visibility: `full` (default) / `minimal` (status bar only) / `hidden` (no sticky, no bumping) |
 | `lifecycle` | No | Session status posts — idle warning, timeout, pause, resume, and the shutdown notice a deploy leaves in each open thread: `full` (default, all of them) / `minimal` (drops the idle warning, which predicts a timeout the next message would undo anyway) / `hidden` (none). Editing a status post the thread already has is not suppressed at any level: it adds no post and no notification, and leaving a stale "session idle" up across a restart would be worse. ⚠️ An **abnormal exit** (`[Exited: <code>]`, non-zero only) posts at every level including `hidden`: it is a failure report, and silencing it would make a session that died look exactly like one that finished. Note that `hidden` also removes the post a 🔄 reaction resumes from — sending a message in the thread still resumes it, and the channel sticky says so. |
+| `lifecycleDelivery` | No | How a **new** lifecycle notice reaches the thread: `post` (default, a new post as before) / `dedup` (no new post when the bot's last post in the thread already shows the same notice: that post is updated to the new text in place instead, which notifies nobody; a "Session resumed" notice counts as the shutdown notice the next restart would post, so back-to-back restarts leave one post) / `reaction` (an emoji on the bot's last post instead of a new post, which notifies nobody: ⏳ idle, ⏰ timed out, 💤 paused, 🔌 shutting down, 🌅 resumed; when that last post is a notice the bot had to post itself, it is updated in place instead, so its text and emoji never disagree). `lifecycle` still decides whether a notice is wanted at all, so `hidden` delivers nothing. Editing an existing status post is unchanged, except that a post carrying the notice as a reaction is never rewritten (its emoji is swapped instead). The deduped or reacted-to post is what a 🔄 reaction resumes the session from. With nothing to react to yet (right after a restart, before the bot has posted), the notice is posted. Any newer post in the thread, by anyone, ends a notice's turn as the last post, so a later notice is never refreshed above it. Under `reaction` the emoji only goes on Claude's reply or a task-list post; on a question, a plan or a prompt the reactions are the answers, so the notice is posted instead, as it is when an emoji swap fails. Posts made while the bot is down are not seen. `reaction` also drops the notice's text, such as "react 🔄 to resume" and the minutes left. ⚠️ An **abnormal exit** always posts, whatever this is set to. |
 | `directChannelMode` | No | Direct channel mode: the whole channel is one session, and the bot replies with top-level channel posts instead of thread replies. `true` for defaults, or an options object (`respondTo`). See [Direct Channel Mode](#direct-channel-mode). |
 | `approvals` | No | Who may answer tool-permission prompts and other reaction gates: `owner` (session participants) or `all_users` (everyone on `allowedUsers`). Unset keeps the historical default per mode — `all_users` for thread sessions, `owner` for direct channel mode. See [Approvals](#approvals). |
 | `ackReaction` | No | Read receipt: react to every accepted message (session start, follow-up, resume) the instant it is accepted, before Claude produces output. `true` uses 👀 (`eyes`), a string names a custom emoji. Persistent, unlike the typing indicator — useful in busy channels and for messages queued behind an in-flight session start. The receipt means *accepted*, not *delivered*: a later failure (capacity limit, Claude not coming up) is still reported by its own post. `!commands` are not acked — they have their own immediate feedback, and neither are messages accepted through the message-approval flow (an authorized user approving a non-participant's message) — there the approval reaction is already the visible signal. Note: in direct channel mode this is one reaction API call per accepted message. Default off. |
@@ -199,6 +200,7 @@ What happens: every `audio/*` attachment (or a file with an audio extension when
 | `sessionHeader` | No | Per-thread header visibility: `full` (default) / `minimal` (status bar only) / `hidden` (no header post) |
 | `stickyMessage` | No | Channel sticky visibility: `full` (default) / `minimal` (status bar only) / `hidden` (no sticky, no bumping) |
 | `lifecycle` | No | Session status posts — idle warning, timeout, pause, resume, and the shutdown notice a deploy leaves in each open thread: `full` (default, all of them) / `minimal` (drops the idle warning, which predicts a timeout the next message would undo anyway) / `hidden` (none). Editing a status post the thread already has is not suppressed at any level: it adds no post and no notification, and leaving a stale "session idle" up across a restart would be worse. ⚠️ An **abnormal exit** (`[Exited: <code>]`, non-zero only) posts at every level including `hidden`: it is a failure report, and silencing it would make a session that died look exactly like one that finished. Note that `hidden` also removes the post a 🔄 reaction resumes from — sending a message in the thread still resumes it, and the channel sticky says so. |
+| `lifecycleDelivery` | No | How a **new** lifecycle notice reaches the thread: `post` (default, a new post as before) / `dedup` (no new post when the bot's last post in the thread already shows the same notice: that post is updated to the new text in place instead, which notifies nobody; a "Session resumed" notice counts as the shutdown notice the next restart would post, so back-to-back restarts leave one post) / `reaction` (an emoji on the bot's last post instead of a new post, which notifies nobody: ⏳ idle, ⏰ timed out, 💤 paused, 🔌 shutting down, 🌅 resumed; when that last post is a notice the bot had to post itself, it is updated in place instead, so its text and emoji never disagree). `lifecycle` still decides whether a notice is wanted at all, so `hidden` delivers nothing. Editing an existing status post is unchanged, except that a post carrying the notice as a reaction is never rewritten (its emoji is swapped instead). The deduped or reacted-to post is what a 🔄 reaction resumes the session from. With nothing to react to yet (right after a restart, before the bot has posted), the notice is posted. Any newer post in the thread, by anyone, ends a notice's turn as the last post, so a later notice is never refreshed above it. Under `reaction` the emoji only goes on Claude's reply or a task-list post; on a question, a plan or a prompt the reactions are the answers, so the notice is posted instead, as it is when an emoji swap fails. Posts made while the bot is down are not seen. `reaction` also drops the notice's text, such as "react 🔄 to resume" and the minutes left. ⚠️ An **abnormal exit** always posts, whatever this is set to. |
 | `directChannelMode` | No | Direct channel mode: the whole channel is one session, and the bot replies with top-level channel posts instead of thread replies. `true` for defaults, or an options object (`respondTo`). See [Direct Channel Mode](#direct-channel-mode). |
 | `approvals` | No | Who may answer tool-permission prompts and other reaction gates: `owner` (session participants) or `all_users` (everyone on `allowedUsers`). Unset keeps the historical default per mode — `all_users` for thread sessions, `owner` for direct channel mode. See [Approvals](#approvals). |
 | `ackReaction` | No | Read receipt: react to every accepted message (session start, follow-up, resume) the instant it is accepted, before Claude produces output. `true` uses 👀 (`eyes`), a string names a custom emoji. Persistent, unlike the typing indicator — useful in busy channels and for messages queued behind an in-flight session start. The receipt means *accepted*, not *delivered*: a later failure (capacity limit, Claude not coming up) is still reported by its own post. `!commands` are not acked — they have their own immediate feedback, and neither are messages accepted through the message-approval flow (an authorized user approving a non-participant's message) — there the approval reaction is already the visible signal. Note: in direct channel mode this is one reaction API call per accepted message. Default off. |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-threads",
-  "version": "1.40.2",
+  "version": "1.41.0",
   "description": "Run Claude Code from Slack or Mattermost. Sessions stream live into threads where your whole team can watch and steer.",
   "main": "dist/index.js",
   "type": "module",
@@ -85,7 +85,7 @@
     "react": "^19.3.1",
     "semver": "7.8.5",
     "update-notifier": "^7.3.1",
-    "ws": "8.22.0",
+    "ws": "8.22.1",
     "zod": "^4.6.7"
   },
   "devDependencies": {
@@ -101,7 +101,7 @@
     "@types/ws": "^8.18.2",
     "eslint": "^10.13.0",
     "husky": "^9.1.7",
-    "knip": "6.43.0",
+    "knip": "6.44.1",
     "lint-staged": "^17.0.4",
     "prettier": "^3.9.10",
     "react-devtools-core": "^8.0.0",