@integrity-labs/agt-cli 0.28.355 → 0.28.357

package/dist/lib/manager-worker.js

@@ -48,7 +48,7 @@ import {
   safeWriteJsonAtomic,
   setConfigHash,
   toOpencodeModel
-} from "../chunk-R2D4AQGX.js";
+} from "../chunk-GAWEPU6C.js";
 import {
   getProjectDir as getProjectDir2,
   getReadyTasks,
@@ -9460,7 +9460,7 @@ var agentRestartTimezoneInputs = /* @__PURE__ */ new Map();
 var lastVersionCheckAt = 0;
 var VERSION_CHECK_INTERVAL_MS = 5 * 60 * 1e3;
 var lastResponsivenessProbeAt = 0;
-var agtCliVersion = true ? "0.28.355" : "dev";
+var agtCliVersion = true ? "0.28.357" : "dev";
 function resolveBrewPath(execFileSync2) {
   try {
     const out = execFileSync2("which", ["brew"], { timeout: 5e3 }).toString().trim();

package/dist/mcp/slack-channel.js

@@ -37361,13 +37361,22 @@ function buildSlackMcpInstructions(opts) {
     "Address users by user_name, never raw user ID. In multi-participant threads the CURRENT speaker is on the latest <channel> tag.",
     `Reactions (slack.react sparingly - prefer a reply): :${ackReaction}: = ack (auto-added on inbound, don't duplicate); \u2705 = success.` + (skipReactionOn ? ` "${skipReaction}" = seen, not replying.` : "") + " NEVER react to signal failure of your work - on failure slack.reply one sentence explaining it (no stack traces/secrets). \u23F3 and \u274C are system-only; never add them.",
     skipReactionOn ? `Decided NOT to reply to a DM or thread message (different @-mention, side chat, auto_followed catch-up, nothing useful)? slack.react with "${skipReaction}" so the sender knows you saw it - never post "this wasn't for me". Top-level channel messages you may skip silently.` : "A thread message NOT addressed to you (different @-mention, side chat, auto_followed catch-up): SILENTLY SKIP - no reaction, no reply.",
-    'auto_followed="true" \u2192 reply only if useful OR your bot user is @-mentioned. Deliver a file: save under your project dir, call slack.upload_file with path + channel + inbound_id.'
+    'auto_followed="true" \u2192 reply only if useful (self-mentions auto-cleared server-side). own_bot_user_id=your Slack user ID. File: slack.upload_file path+channel+inbound_id.'
   ].join(" ");
 }
 
 // src/slack-react-taxonomy.ts
 var SLACK_REACT_TOOL_DESCRIPTION = "Add an emoji reaction to a Slack message. Use sparingly \u2014 prefer a text reply. Reaction taxonomy: \u2705 = action completed successfully. \u{1F4DD} (:memo:) and \u26A0\uFE0F (:warning:) are blessed for explicit multi-state STATUS pipelines only \u2014 e.g. marking a run/parent \u2705 done / \u{1F4DD} waiting / \u26A0\uFE0F failed for at-a-glance status. That exception is narrow: never use a reaction to tell a user that YOUR reply failed \u2014 NEVER react to signal failure of your own work; on failure call slack.reply with one sentence explaining what went wrong instead (no stack traces, no secrets). \u{1F440} (eyes) is already auto-applied on inbound; do not duplicate. \u23F3 (:hourglass_flowing_sand:) is reserved for the system to mark an inbound that arrived while the agent couldn't reply \u2014 never add \u23F3 or \u274C yourself. (A \u{1F512} you may see on a thread is the server's reply-throttle marker, not a coerced reaction \u2014 slack.react passes your emoji straight through to Slack and never rewrites it to \u{1F512}.)";
 
+// src/slack-routed-to-note.ts
+function describeChannelRedirect(input) {
+  const { requestedChannel, effectiveChannel, reason = null } = input;
+  if (!requestedChannel) return null;
+  if (requestedChannel === effectiveChannel) return null;
+  const why = reason === "scheduled-task" ? " (routed to the scheduled task's configured destination)" : reason === "dm-channel-guard" ? " (redirected by the DM-channel guard because those coordinates belong to a DM)" : "";
+  return `Heads up: this was delivered to ${effectiveChannel}, NOT the ${requestedChannel} you named${why}. routed_to=${effectiveChannel}. If ${effectiveChannel} is not where you intended this to go, the destination is misconfigured; do not assume it posted to ${requestedChannel}.`;
+}
+
 // src/slack-reply-binding-telemetry.ts
 import { readFileSync as readFileSync13, writeFileSync as writeFileSync10 } from "fs";
 import { join as join13 } from "path";
@@ -40845,7 +40854,7 @@ async function resolveBotUserIdOrThrow() {
   err.authFailed = sawAuthFailure;
   throw err;
 }
-var botUserId = null;
+var botUserId = (process.env.SLACK_OWN_BOT_USER_ID ?? "").trim() || null;
 var slackBotUserIdClient = createSlackBotUserIdClient({
   agtHost: AGT_HOST,
   agtApiKey: AGT_API_KEY,
@@ -41451,6 +41460,12 @@ mcp.setRequestHandler(CallToolRequestSchema, async (req) => {
       if (hotThreadRedirected) {
         base += ". Note: this was threaded into the conversation you are actively working in rather than posted at the channel root. If you genuinely meant to start a NEW top-level topic, resend with to_channel_root:true.";
       }
+      const redirectNote = describeChannelRedirect({
+        requestedChannel: channel,
+        effectiveChannel,
+        reason: scheduledDest?.retargeted ? "scheduled-task" : channelGuard.corrected ? "dm-channel-guard" : null
+      });
+      if (redirectNote) base += `. ${redirectNote}`;
       const sentTs = typeof data.ts === "string" ? data.ts : void 0;
       return {
         content: [{ type: "text", text: sentTs ? `${base} (ts=${sentTs})` : base }]
@@ -43001,10 +43016,12 @@ async function connectSocketMode() {
         });
       }
       const isAutoFollowed = !isDirectMessage && evt.type === "message" && isThreadReply && !!threadKey && trackedThreads.has(threadKey);
+      const isSelfMentioned = !!botUserId && text.includes(`<@${botUserId}>`);
+      const effectiveIsAutoFollowed = isAutoFollowed && !isSelfMentioned;
       const shouldEngage = decideSlackEngagement({
         type: evt.type ?? "message",
         text,
-        isAutoFollowed,
+        isAutoFollowed: effectiveIsAutoFollowed,
         botUserId
       });
       const participantEntry = threadKey ? trackedThreads.get(threadKey) : void 0;
@@ -43140,7 +43157,13 @@ ${forwarded.text}` : forwarded.text;
           // !shouldEngage) owes no reply. Additive only; no consumer gates on
           // these yet (Slice 2).
           ...conversationalLaneMeta(shouldEngage),
-          ...isAutoFollowed ? { auto_followed: "true" } : {},
+          // ENG-7919: surface the effective auto-follow state (already cleared when
+          // the bot was @-mentioned) so the agent sees auto_followed="true" only
+          // when the message genuinely requires discretionary engagement judgment.
+          // Also inject own_bot_user_id so the agent can identify self-mentions in
+          // future without relying on external directory lookups.
+          ...effectiveIsAutoFollowed ? { auto_followed: "true" } : {},
+          ...botUserId ? { own_bot_user_id: botUserId } : {},
           // Only set these when we actually have attachments to avoid
           // bloating every notification with empty metadata.
           ...fileMeta.length > 0 ? { files: JSON.stringify(fileMeta) } : {},

package/package.json

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