claude-threads 1.18.0 → 1.18.1

package/CHANGELOG.md

@@ -5,6 +5,11 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.18.1] - 2026-07-17
+
+### Changed
+- **`react_to_post` resolves the triggering message server-side instead of via a per-message permalink.** v1.18.0 fixed `react_to_post` always landing on the thread root by prepending a `[message permalink: ...]` line to every follow-up message's content — correct, but paid for on every single message in every thread even though reactions are occasional. `url` is now optional: when omitted, the MCP server resolves it to the most recent message in the session's own thread via the same `readThread` call `list_thread` already uses, so no per-message metadata needs to ride along in message content at all. (Mattermost and Slack `readThread` apply `limit` differently — Mattermost takes the newest N, Slack's `conversations.replies` paginates from the thread root forward — so the resolver fetches the default page and takes the last element on both platforms rather than relying on `limit: 1`.)
+
 ## [1.18.0] - 2026-07-17
 
 ### Added

package/dist/index.js

@@ -80908,10 +80908,6 @@ async function startUI(options) {
 init_logger();
 
 // src/message-handler.ts
-function withMessagePermalink(client, post2, content) {
-  return `[message permalink: ${client.getPostPermalink(post2)}]
-${content}`;
-}
 async function handleMessage(client, session, post2, user, options) {
   const { platformId, logger, onKill } = options;
   const username = user?.username || "unknown";
@@ -81008,10 +81004,8 @@ async function handleMessage(client, session, post2, user, options) {
         return;
       }
       const files2 = post2.metadata?.files;
-      if (content || files2?.length) {
-        const contentForAgent = content && post2.id !== threadRoot ? withMessagePermalink(client, post2, content) : content;
-        await session.sendFollowUp(threadRoot, contentForAgent, files2, username, user?.displayName);
-      }
+      if (content || files2?.length)
+        await session.sendFollowUp(threadRoot, content, files2, username, user?.displayName);
       return;
     }
     const hasPausedSession = session.registry.getPersistedByThreadId(threadRoot) !== undefined;

package/dist/mcp/mcp-server.js

@@ -57637,7 +57637,7 @@ var readPostInputSchema = {
   max_messages: exports_external.coerce.number().int().optional().describe(`Maximum thread messages to return when include_thread is true. Defaults to ${DEFAULT_THREAD_LIMIT}, capped at ${MAX_THREAD_LIMIT}.`)
 };
 var reactToPostInputSchema = {
-  url: exports_external.string().describe("Permalink URL to a post the bot can already see (its own channel, or a public channel on the same instance). " + "To react to a specific user message (e.g. to acknowledge the one that triggered the current task), use the " + "per-message permalink provided in that message's context — do NOT default to the thread-root permalink."),
+  url: exports_external.string().optional().describe("Permalink URL to a post the bot can already see (its own channel, or a public channel on the same instance). " + "Omit to react to the most recent message in the current session thread (e.g. to acknowledge the message " + "that triggered the current task) — this is the common case and does NOT default to the thread root."),
   emoji: exports_external.string().describe("Emoji name without colons, e.g. 'white_check_mark', '+1', 'eyes'. Platform-specific vocabulary applies.")
 };
 var updateOwnPostInputSchema = {
@@ -57785,6 +57785,27 @@ async function handleReadPost(args) {
   });
 }
 var EMOJI_NAME_RE = /^[a-z0-9_+-]{1,64}$/i;
+async function resolveLatestThreadPost(cfg) {
+  if (!cfg.api.readThread) {
+    return { ok: false, reason: "this platform does not support reading threads" };
+  }
+  if (!cfg.sessionThreadId) {
+    return { ok: false, reason: "no session thread to react in — pass a permalink URL instead" };
+  }
+  let thread;
+  try {
+    thread = await cfg.api.readThread(cfg.sessionThreadId);
+  } catch (err) {
+    const reason = err instanceof Error ? err.message : String(err);
+    mcpLogger.warn(`react_to_post: failed to resolve latest thread message: ${reason}`);
+    return { ok: false, reason };
+  }
+  const latest = thread.at(-1);
+  if (!latest) {
+    return { ok: false, reason: "session thread is empty — pass a permalink URL instead" };
+  }
+  return { ok: true, post: latest };
+}
 async function handleReactToPostWith(args, cfg) {
   if (!cfg.api.addReaction) {
     return { ok: false, reason: "this platform does not support adding reactions" };
@@ -57795,7 +57816,7 @@ async function handleReactToPostWith(args, cfg) {
       reason: `invalid emoji name '${args.emoji}' — use names like 'white_check_mark' or '+1'`
     };
   }
-  const resolved = await resolvePostFromUrl(args.url, cfg);
+  const resolved = args.url ? await resolvePostFromUrl(args.url, cfg) : await resolveLatestThreadPost(cfg);
   if (!resolved.ok)
     return { ok: false, reason: resolved.reason };
   try {
@@ -57812,7 +57833,8 @@ async function handleReactToPost(args) {
     api: getApi(),
     platformUrl: PLATFORM_URL,
     platformType: PLATFORM_TYPE,
-    channelId: PLATFORM_CHANNEL_ID
+    channelId: PLATFORM_CHANNEL_ID,
+    sessionThreadId: PLATFORM_THREAD_ID
   });
 }
 async function handleUpdateOwnPostWith(args, cfg) {
@@ -58364,7 +58386,7 @@ async function main() {
       content: [{ type: "text", text: JSON.stringify(result) }]
     };
   });
-  server.tool("react_to_post", "Add an emoji reaction to a post on the chat platform. Use this to acknowledge a request " + "(✅), flag something ambiguous (\uD83D\uDC40), mark a triggering message done, etc. The post must be in " + "the bot's own channel or in a public channel on the same instance. Returns { ok: true } on " + "success or { ok: false, reason } on failure.", reactToPostInputSchema, async ({ url: url2, emoji: emoji4 }) => {
+  server.tool("react_to_post", "Add an emoji reaction to a post on the chat platform. Use this to acknowledge a request " + "(✅), flag something ambiguous (\uD83D\uDC40), mark a triggering message done, etc. Omit `url` to react " + "to the most recent message in the current session thread — the common case. The post must be " + "in the bot's own channel or in a public channel on the same instance. Returns { ok: true } on " + "success or { ok: false, reason } on failure.", reactToPostInputSchema, async ({ url: url2, emoji: emoji4 }) => {
     const result = await handleReactToPost({ url: url2, emoji: emoji4 });
     return {
       content: [{ type: "text", text: JSON.stringify(result) }]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-threads",
-  "version": "1.18.0",
+  "version": "1.18.1",
   "description": "Share Claude Code sessions live in a Mattermost channel with interactive features",
   "main": "dist/index.js",
   "type": "module",