@integrity-labs/agt-cli 0.28.731 → 0.28.732

package/dist/bin/agt.js

@@ -41,7 +41,7 @@ import {
   success,
   table,
   warn
-} from "../chunk-YNIRFRQE.js";
+} from "../chunk-DGIYNBDG.js";
 import {
   getProjectDir,
   isSessionResumeDisabled,
@@ -5467,7 +5467,7 @@ import { execFileSync, execSync } from "child_process";
 import { existsSync as existsSync11, realpathSync as realpathSync2 } from "fs";
 import chalk18 from "chalk";
 import ora16 from "ora";
-var cliVersion = true ? "0.28.731" : "dev";
+var cliVersion = true ? "0.28.732" : "dev";
 async function fetchLatestVersion() {
   const host2 = getHost();
   if (!host2) return null;
@@ -6654,7 +6654,7 @@ function handleError(err) {
 }
 
 // src/bin/agt.ts
-var cliVersion2 = true ? "0.28.731" : "dev";
+var cliVersion2 = true ? "0.28.732" : "dev";
 var program = new Command();
 program.name("agt").description("Augmented CLI \u2014 agent provisioning and management").version(cliVersion2).option("--json", "Emit machine-readable JSON output (suppress spinners and colors)").option("--skip-update-check", "Skip the automatic update check on startup");
 program.hook("preAction", async (thisCommand, actionCommand) => {

package/dist/{chunk-YNIRFRQE.js → chunk-DGIYNBDG.js}

@@ -6427,7 +6427,7 @@ function exchangeFailureKind(err) {
 }
 
 // src/lib/api-client.ts
-var agtCliVersion = true ? "0.28.731" : "dev";
+var agtCliVersion = true ? "0.28.732" : "dev";
 var lastConfigHash = null;
 function setConfigHash(hash) {
   lastConfigHash = hash && hash.length > 0 ? hash : null;
@@ -10473,4 +10473,4 @@ export {
   managerInstallSystemUnitCommand,
   managerUninstallSystemUnitCommand
 };
-//# sourceMappingURL=chunk-YNIRFRQE.js.map
+//# sourceMappingURL=chunk-DGIYNBDG.js.map

package/dist/lib/manager-worker.js

@@ -57,7 +57,7 @@ import {
   safeWriteJsonAtomic,
   setConfigHash,
   tripClass
-} from "../chunk-YNIRFRQE.js";
+} from "../chunk-DGIYNBDG.js";
 import {
   getProjectDir as getProjectDir2,
   getReadyTasks,
@@ -12995,7 +12995,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.731" : "dev";
+var agtCliVersion = true ? "0.28.732" : "dev";
 function resolveBrewPath(execFileSync3) {
   try {
     const out = execFileSync3("which", ["brew"], { timeout: 5e3 }).toString().trim();

package/dist/mcp/direct-chat-channel.js

@@ -38165,6 +38165,20 @@ async function readCursorAdvanceBody(res) {
   };
 }
 
+// src/direct-chat-mcp-instructions.ts
+function buildDirectChatMcpInstructions() {
+  return [
+    "CRITICAL: every response to a direct-chat <channel> tag MUST go through direct_chat.reply (passing the session_id verbatim). Text in your session WITHOUT a direct_chat.reply call never reaches the operator \u2014 the reply dies inside the agent process.",
+    'Messages from the webapp Direct Chat arrive as <channel source="direct-chat" session_id="..." user="...">.',
+    "When the tag carries user_name (and sometimes user_email / user_role), that is the verified human you are talking with; address them by name and tailor your reply to who they are. If those attributes are absent, the sender is unknown, so just reply helpfully without personalization.",
+    "Reply using the direct_chat.reply tool, passing the session_id from the tag.",
+    "Always reply to every direct chat message that expects a reply (its meta has requires_reply=true, or no requires_reply field) \u2014 the user is waiting in the webapp.",
+    "NEVER call direct_chat.reply for a NOTICE \u2014 a notification whose meta has requires_reply=false (ENG-6381). It is an informational FYI (e.g. an integration-status update), not a question, and it has ALREADY been acknowledged for you. Replying would wrongly post into the operator\u2019s chat history and burn a turn. Just take it into account and carry on.",
+    "In the rare case you deliberately handle a reply-expecting message without replying (e.g. an internal command), call direct_chat.consume with the session_id so it is not treated as undelivered and redelivered.",
+    "Keep replies concise and helpful. You have full access to all your MCP tools."
+  ].join(" ");
+}
+
 // src/usage-limit-reactive-decision.ts
 import { createHash } from "crypto";
 function shouldArmWatch(opts) {
@@ -38531,23 +38545,12 @@ var mcp = new Server(
       experimental: { "claude/channel": {} },
       tools: {}
     },
-    instructions: [
-      // ENG-5845: highest-priority guard first. Without this framing,
-      // Opus 4.8 reads the softer "Reply using…" line as a suggestion and
-      // emits plain text — the reply lives in the local Claude session
-      // but never reaches the operator's session_id through the channel
-      // API. Mirrors the slack-channel CRITICAL line shipped in
-      // ENG-5830. Total instructions string is ~850 / 2048 chars so we
-      // have room to be explicit.
-      "CRITICAL: every response to a direct-chat <channel> tag MUST go through direct_chat.reply (passing the session_id verbatim). Text in your session WITHOUT a direct_chat.reply call never reaches the operator \u2014 the reply dies inside the agent process.",
-      'Messages from the webapp Direct Chat arrive as <channel source="direct-chat" session_id="..." user="...">.',
-      "When the tag carries user_name (and sometimes user_email / user_role), that is the verified human you are talking with; address them by name and tailor your reply to who they are. If those attributes are absent, the sender is unknown, so just reply helpfully without personalization.",
-      "Reply using the direct_chat.reply tool, passing the session_id from the tag.",
-      "Always reply to every direct chat message that expects a reply (its meta has requires_reply=true, or no requires_reply field) \u2014 the user is waiting in the webapp.",
-      "NEVER call direct_chat.reply for a NOTICE \u2014 a notification whose meta has requires_reply=false (ENG-6381). It is an informational FYI (e.g. an integration-status update), not a question, and it has ALREADY been acknowledged for you. Replying would wrongly post into the operator\u2019s chat history and burn a turn. Just take it into account and carry on.",
-      "In the rare case you deliberately handle a reply-expecting message without replying (e.g. an internal command), call direct_chat.consume with the session_id so it is not treated as undelivered and redelivered.",
-      "Keep replies concise and helpful. You have full access to all your MCP tools."
-    ].join(" ")
+    // NOTE: Claude Code truncates MCP server instructions at 2048 chars.
+    // ENG-9649: built by a pure, length-tested builder
+    // (direct-chat-mcp-instructions.ts). The budget used to be tracked in a
+    // comment here, which had drifted 668 chars out of date without anything
+    // noticing.
+    instructions: buildDirectChatMcpInstructions()
   }
 );
 var claimTracker = new DirectChatClaimTracker();

package/dist/mcp/telegram-channel.js

@@ -40533,6 +40533,24 @@ async function actuateHostRestart(opts) {
   }
 }
 
+// src/telegram-mcp-instructions.ts
+var MAX_SKIP_REACTION_UNITS = 8;
+var REACT_POLICY = `Reacting is egress and does NOT settle anything \u2014 telegram.consume is what settles. Never react in a chat you are barred from, and never post a "this wasn't for me" message.`;
+function buildTelegramMcpInstructions(opts) {
+  const emoji2 = opts.skipReaction ?? "";
+  const skipReactionOn = opts.skipReactionOn && emoji2.length > 0 && emoji2.length <= MAX_SKIP_REACTION_UNITS;
+  return [
+    "CRITICAL: every response to a Telegram <channel> tag MUST go through telegram.reply with the chat_id from the tag \u2014 typed text never reaches the user. Slow work: interim ack (telegram.reply interim:true), then your FINAL answer as a separate telegram.reply (interim omitted). An ack is not the answer.",
+    'Messages from Telegram arrive as <channel source="telegram" chat_id="..." user="..." user_name="..." message_id="...">. Pass reply_to_message_id from the tag so the response lands as a quote-reply in busy chats.',
+    "Deliberately NOT replying (a standing rule bars you from that chat, or the message only changed state)? Call telegram.consume with the chat_id and a short reason: it settles the message without posting anything. Without a reply or a consume it counts as undelivered and re-delivers to you forever.",
+    "Inbound attachments: `files` on the tag is a JSON string \u2014 JSON.parse it. An entry with `path` (or top-level `image_path`) is already downloaded \u2014 Read it. Entries with `file_id` and no `path` need telegram.download_attachment (file_id + chat_id), then Read the returned path.",
+    'For work >30s follow the CLAUDE.md kanban flow: kanban_add \u2192 reply "On it \u2014 tracking here: <kanban URL>" \u2192 in_progress \u2192 reply the result. Simple lookups skip kanban but still reply.',
+    "Address users by user_name; user is the numeric Telegram ID. Resolve ambiguous times against your own Timezone from CLAUDE.md \u2014 do not ask.",
+    "Reactions (telegram.react sparingly \u2014 prefer a reply): \u{1F440} = ack (auto-added, do not duplicate); \u{1F44D} or \u{1F389} = success." + (skipReactionOn ? ` ${emoji2} = seen, not replying.` : "") + " NEVER react to signal failure of YOUR work \u2014 telegram.reply one sentence explaining it. Free-tier emoji only: \u{1F44D} \u{1F44E} \u2764 \u{1F525} \u{1F389} \u{1F64F} \u{1F44C} \u{1F440} \u{1F4AF} \u{1FAE1}.",
+    skipReactionOn ? `${REACT_POLICY} Where engaging IS permitted you may also telegram.react "${emoji2}" after consuming.` : REACT_POLICY
+  ].filter(Boolean).join(" ");
+}
+
 // src/telegram-channel.ts
 function redactId(id) {
   return createHash3("sha256").update(String(id)).digest("hex").slice(0, 8);
@@ -42953,19 +42971,14 @@ var mcp = new Server(
       tools: {}
     },
     // NOTE: Claude Code truncates MCP server instructions at 2048 chars.
-    // Attachments rules live near the top because they get chopped otherwise
-    // and the agent silently loses attachment-handling guidance.
-    instructions: [
-      // Highest-priority lines first — Claude Code truncates this string at
-      // 2048 chars, so anything appended late silently disappears.
-      "CRITICAL: every response to a Telegram <channel> tag MUST go through telegram.reply with the chat_id from the tag \u2014 typed text never reaches the user. Slow work: interim ack (telegram.reply interim:true), then your FINAL answer as a separate telegram.reply (interim omitted). An ack is not the answer.",
-      'Messages from Telegram arrive as <channel source="telegram" chat_id="..." user="..." user_name="..." message_id="...">. Pass reply_to_message_id from the tag so the response lands as a quote-reply in busy chats.',
-      "Inbound attachments: <channel> `files` is a JSON-serialised array \u2014 JSON.parse it. If an entry has `path`, the image is already downloaded \u2014 Read it directly, do NOT call telegram.download_attachment. Use that tool only for entries with `file_id` but NO `path` (PDF, docx, voice, audio, video, animations): pass file_id + chat_id verbatim, then Read the returned path. Single-image messages also get a top-level `image_path`. Caption arrives as channel content. Don't surface internal file-handling errors that don't affect the answer.",
-      'For work >30s follow CLAUDE.md kanban flow: kanban_add \u2192 reply "On it \u2014 tracking here: <kanban URL>" \u2192 move to in_progress \u2192 do the work \u2192 reply with the result. Simple lookups skip kanban but still reply.',
-      "Address users by user_name; user is the numeric Telegram ID. Resolve ambiguous times against your own Timezone from CLAUDE.md \u2014 do not ask.",
-      "Reaction taxonomy (use telegram.react sparingly \u2014 prefer telegram.reply): \u{1F440} = ack (already auto-added on inbound, do not duplicate); \u{1F44D} or \u{1F389} = success." + (SKIP_REACTION_ON ? ` ${TELEGRAM_SKIP_REACTION} = seen but not replying (see below).` : "") + ` NEVER react to signal failure of YOUR work. On failure, telegram.reply with one sentence explaining what went wrong. Free-tier emoji: \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}. (If a message arrived while you were offline you may see a system-posted "can't respond right now" notice \u2014 that's the runtime, not you; don't repeat or apologise for it.)`,
-      SKIP_REACTION_ON ? `When you read a message you decide NOT to reply to (nothing useful to add): call telegram.react with emoji "${TELEGRAM_SKIP_REACTION}" so the sender knows you saw it \u2014 never post a "this wasn't for me" message.` : ""
-    ].filter(Boolean).join(" ")
+    // ENG-9649: built by a pure, length-tested builder
+    // (telegram-mcp-instructions.ts) so a line can no longer fall off the end
+    // unnoticed — which is exactly what happened to the do-not-reply guidance
+    // while the reaction taxonomy went on pointing at it.
+    instructions: buildTelegramMcpInstructions({
+      skipReactionOn: SKIP_REACTION_ON,
+      skipReaction: TELEGRAM_SKIP_REACTION
+    })
   }
 );
 mcp.setRequestHandler(ListToolsRequestSchema, async () => ({

package/package.json

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