@integrity-labs/agt-cli 0.15.6 → 0.15.8

package/mcp/index.js

@@ -21040,6 +21040,12 @@ var AGT_API_KEY = process.env.AGT_API_KEY;
 var AGT_AGENT_ID = process.env.AGT_AGENT_ID;
 var AGT_AGENT_CODE_NAME = process.env.AGT_AGENT_CODE_NAME;
 var AGT_APP_URL = (process.env.AGT_APP_URL ?? "").replace(/\/+$/, "");
+function readRunId() {
+  const raw = process.env.AGT_RUN_ID ?? "";
+  if (!raw || raw === "${AGT_RUN_ID}") return null;
+  return raw;
+}
+var AGT_RUN_ID = readRunId();
 var AGT_TOKEN = process.env.AGT_TOKEN ?? "";
 if (!AGT_HOST || !AGT_AGENT_ID || !AGT_TOKEN && !AGT_API_KEY) {
   console.error(
@@ -21166,6 +21172,7 @@ server.tool(
   async (params) => {
     const data = await apiPost("/host/kanban", {
       agent_id: AGT_AGENT_ID,
+      run_id: AGT_RUN_ID,
       add: [
         {
           title: params.title,
@@ -21791,6 +21798,8 @@ server.tool(
   async (params) => {
     const data = await apiPost("/host/knowledge", {
       agent_id: AGT_AGENT_ID,
+      // ENG-4538 will land a run_id column on team_knowledge; until then
+      // the /host/knowledge endpoint has nowhere to stamp AGT_RUN_ID.
       add: [
         {
           title: params.title,

package/mcp/slack-channel.js

@@ -14156,17 +14156,21 @@ var ALLOWED_USERS = new Set(
 );
 var THREAD_AUTO_FOLLOW = process.env.SLACK_THREAD_AUTO_FOLLOW ?? "off";
 var CHANNEL_RESPONSE_MODE = parseResponseMode(process.env.SLACK_CHANNEL_RESPONSE_MODE);
-var RESPONSE_TIMEOUT_MS = 12e4;
+var RESPONSE_TIMEOUT_MS = 3e5;
 var pendingMessages = /* @__PURE__ */ new Map();
 function trackPendingMessage(channel, threadTs, messageTs) {
   const key = `${channel}:${threadTs}:${messageTs}`;
   const timer = setTimeout(async () => {
     pendingMessages.delete(key);
     try {
-      await fetch("https://slack.com/api/reactions.add", {
+      await fetch("https://slack.com/api/chat.postMessage", {
         method: "POST",
         headers: { "Content-Type": "application/json", Authorization: `Bearer ${BOT_TOKEN}` },
-        body: JSON.stringify({ channel, timestamp: messageTs, name: "x" })
+        body: JSON.stringify({
+          channel,
+          thread_ts: threadTs,
+          text: "Sorry \u2014 I didn't get a response back to you within 5 minutes, so this one fell on the floor. Please re-send if it's still relevant."
+        })
       });
     } catch {
     }
@@ -14271,8 +14275,8 @@ var mcp = new Server(
       "Address users by user_name, never by raw user ID. In multi-participant threads the CURRENT speaker is the one on the latest <channel> tag \u2014 don't conflate with earlier participants.",
       "Mentioned in a channel \u2192 respond in that thread. DM \u2192 respond directly.",
       'auto_followed="true" messages are from threads you previously joined: reply only if you have something useful to add. Skip if the conversation moved on, the message is directed at someone else, or your input would not add value.',
-      'Reaction taxonomy (use slack.react sparingly \u2014 most messages need a reply, not a reaction): \u{1F440} = ack/working on it (already auto-added on inbound, do not duplicate); \u2705 = action completed successfully; \u274C = you TRIED to execute the requested action and it FAILED with an error. Do NOT use \u274C to mean "skipped", "disagree", "n/a", "not addressed to me", or "no response needed".',
-      `When a message in a thread is not addressed to you (different @-mention, conversation between others, auto_followed catch-up): SILENTLY SKIP \u2014 no reaction, no reply, do nothing. Adding \u274C in this case is wrong; it gives the user a misleading "execution failed" signal when in fact you correctly identified the message wasn't yours to handle.`,
+      "Reaction taxonomy (use slack.react sparingly \u2014 most messages need a reply, not a reaction): \u{1F440} = ack/working on it (already auto-added on inbound, do not duplicate); \u2705 = action completed successfully. NEVER react to signal failure \u2014 users misread emoji reactions and don't know why something failed. If an action failed, send a slack.reply with one sentence explaining what went wrong (no stack traces, no secrets) so the user understands.",
+      `When a message in a thread is not addressed to you (different @-mention, conversation between others, auto_followed catch-up): SILENTLY SKIP \u2014 no reaction, no reply, do nothing. Do NOT post a "this wasn't for me" message and do NOT add a failure reaction; either is misleading.`,
       "To deliver a file, save it under your project dir and call slack.upload_file with path, channel, thread_ts."
     ].join(" ")
   }
@@ -14300,13 +14304,13 @@ mcp.setRequestHandler(ListToolsRequestSchema, async () => ({
     },
     {
       name: "slack.react",
-      description: 'Add an emoji reaction to a Slack message. Use sparingly \u2014 prefer a text reply. Reaction taxonomy: \u2705 = action completed successfully; \u274C (`x`) = you TRIED to execute the requested action and it FAILED with an error. Do NOT use \u274C for "skipped", "disagree", "not addressed to me", "n/a", or "noted" \u2014 those need either a text reply or no response at all. \u{1F440} (eyes) is already auto-applied on inbound; do not duplicate.',
+      description: "Add an emoji reaction to a Slack message. Use sparingly \u2014 prefer a text reply. Reaction taxonomy: \u2705 = action completed successfully. NEVER react to signal failure \u2014 users can't tell why it failed from a reaction. On failure, call slack.reply with one sentence explaining what went wrong instead. \u{1F440} (eyes) is already auto-applied on inbound; do not duplicate.",
       inputSchema: {
         type: "object",
         properties: {
           channel: { type: "string", description: "Slack channel ID" },
           timestamp: { type: "string", description: "Message timestamp to react to" },
-          emoji: { type: "string", description: 'Emoji name without colons (e.g. "white_check_mark", "x"). Only use "x" when an execution attempt actually failed.' }
+          emoji: { type: "string", description: 'Emoji name without colons (e.g. "white_check_mark"). Do NOT use "x" or any other failure emoji \u2014 send a slack.reply explaining the failure instead.' }
         },
         required: ["channel", "timestamp", "emoji"]
       }

package/mcp/telegram-channel.js

@@ -14150,8 +14150,7 @@ function telegramApiCall(method, body, timeoutMs) {
   });
 }
 var ACK_EMOJI = "\u{1F440}";
-var TIMEOUT_EMOJI = "\u{1F494}";
-var RESPONSE_TIMEOUT_MS = 12e4;
+var RESPONSE_TIMEOUT_MS = 3e5;
 async function setMessageReaction(chatId, messageId, emoji2) {
   try {
     const resp = await telegramApiCall(
@@ -14183,7 +14182,29 @@ function trackPendingMessage(chatId, messageId, chatType) {
   if (existing) clearTimeout(existing.timer);
   const timer = setTimeout(() => {
     pendingMessages.delete(key);
-    void setMessageReaction(chatId, messageId, TIMEOUT_EMOJI);
+    void setMessageReaction(chatId, messageId, null);
+    void telegramApiCall(
+      "sendMessage",
+      {
+        chat_id: chatId,
+        text: "Sorry \u2014 I didn't get a response back to you within 5 minutes, so this one fell on the floor. Please re-send if it's still relevant.",
+        reply_to_message_id: Number(messageId),
+        allow_sending_without_reply: true
+      },
+      1e4
+    ).then((resp) => {
+      if (!resp.ok) {
+        process.stderr.write(
+          `telegram-channel(${AGENT_CODE_NAME}): timeout sendMessage failed for chat ${redactId(chatId)} message ${redactId(messageId)}: ${resp.description ?? "unknown"}
+`
+        );
+      }
+    }).catch((err) => {
+      process.stderr.write(
+        `telegram-channel(${AGENT_CODE_NAME}): timeout sendMessage error for chat ${redactId(chatId)} message ${redactId(messageId)}: ${err.message}
+`
+      );
+    });
     process.stderr.write(
       `telegram-channel(${AGENT_CODE_NAME}): response timeout for message ${redactId(messageId)} in chat ${redactId(chatId)}
 `
@@ -14203,11 +14224,21 @@ function clearPendingMessage(chatId, messageId) {
     return;
   }
   const prefix = `${chatId}:`;
+  let clearedPrivate = false;
   for (const [key, entry] of pendingMessages) {
     if (!key.startsWith(prefix)) continue;
     if (entry.chatType !== "private") continue;
     clearTimeout(entry.timer);
     pendingMessages.delete(key);
+    clearedPrivate = true;
+  }
+  if (clearedPrivate) return;
+  for (const [key, entry] of pendingMessages) {
+    if (!key.startsWith(prefix)) continue;
+    if (entry.chatType === "private") continue;
+    clearTimeout(entry.timer);
+    pendingMessages.delete(key);
+    return;
   }
 }
 var mcp = new Server(
@@ -14227,7 +14258,7 @@ var mcp = new Server(
       'For work >30s follow CLAUDE.md kanban flow: kanban.add, reply with "On it \u2014 tracking here: <kanban URL>", move to in_progress, do the work, reply with the result. Simple lookups skip kanban but still reply.',
       "Address users by user_name; user is the numeric Telegram ID. Reply-to a specific message with reply_to_message_id, otherwise omit.",
       "Resolve ambiguous times against your own Timezone from CLAUDE.md \u2014 do not ask the user.",
-      `Reaction taxonomy (use telegram.react sparingly \u2014 prefer a text reply via telegram.reply): \u{1F440} = ack/working on it (already auto-added on inbound, do not duplicate); \u{1F44D} or \u{1F389} = action completed successfully; \u{1F494} = you TRIED to execute the requested action and it FAILED with an error (Telegram's free-tier stand-in for Slack's \u274C; the literal \u274C is not on the bot-allowed emoji list). Do NOT use \u{1F494} for "skipped", "disagree", "n/a", or "no response needed" \u2014 those need either a text reply or no reaction. Free-tier emoji set: \u{1F44D} \u{1F44E} \u2764 \u{1F525} \u{1F389} \u{1F914} \u{1F92F} \u{1F64F} \u{1F44C} \u{1F440} \u{1F4AF} \u270D \u{1FAE1} \u{1F192} \u{1F973} \u{1F494} (premium-only fail silently).`
+      "Reaction taxonomy (use telegram.react sparingly \u2014 prefer a text reply via telegram.reply): \u{1F440} = ack/working on it (already auto-added on inbound, do not duplicate); \u{1F44D} or \u{1F389} = action completed successfully. NEVER react to signal failure \u2014 users misread emoji reactions and don't know why something failed. If an action failed, send a telegram.reply with one sentence explaining what went wrong (no stack traces, no secrets) so the user understands. Free-tier emoji set: \u{1F44D} \u{1F44E} \u2764 \u{1F525} \u{1F389} \u{1F914} \u{1F92F} \u{1F64F} \u{1F44C} \u{1F440} \u{1F4AF} \u270D \u{1FAE1} \u{1F192} \u{1F973} \u{1F494} (premium-only fail silently)."
     ].join(" ")
   }
 );
@@ -14287,7 +14318,7 @@ mcp.setRequestHandler(ListToolsRequestSchema, async () => ({
     },
     {
       name: "telegram.react",
-      description: `Add an emoji reaction to a Telegram message. Use sparingly \u2014 prefer a text reply via telegram.reply. Reaction taxonomy: \u{1F44D} or \u{1F389} = action completed successfully; \u{1F494} = you TRIED to execute the requested action and it FAILED with an error (free-tier stand-in for Slack's \u274C). Do NOT use \u{1F494} for "skipped", "disagree", or "noted" \u2014 those need a text reply or no reaction at all. \u{1F440} is already auto-applied on inbound; do not duplicate. Only free-tier emoji reactions are available to bots (Premium-only emoji fail silently). Pass an empty string or omit emoji to clear the bot's reaction on that message.`,
+      description: "Add an emoji reaction to a Telegram message. Use sparingly \u2014 prefer a text reply via telegram.reply. Reaction taxonomy: \u{1F44D} or \u{1F389} = action completed successfully. NEVER react to signal failure \u2014 users can't tell why it failed from a reaction. On failure, call telegram.reply with one sentence explaining what went wrong instead. \u{1F440} is already auto-applied on inbound; do not duplicate. Only free-tier emoji reactions are available to bots (Premium-only emoji fail silently). Pass an empty string or omit emoji to clear the bot's reaction on that message.",
       inputSchema: {
         type: "object",
         properties: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integrity-labs/agt-cli",
-  "version": "0.15.6",
+  "version": "0.15.8",
   "description": "Augmented Team CLI — agent provisioning and management",
   "type": "module",
   "engines": {